Apparatus and methods for content delivery and message exchange across multiple content delivery networks

ABSTRACT

Methods and apparatus for providing protected content to subscribers of a managed (e.g., MSO) network via a content source accessible via an internetwork such as the Internet. In one embodiment, a user accesses a service provider portal (e.g., website), and requests content. The service provider determines whether the requesting user is permitted to access the content, and what rights or restrictions are associated with the user. This includes authenticating the user as a subscriber of the MSO, and determining the subscriber&#39;s subscription level. In another embodiment, a user&#39;s account with the MSO and service provider may be federated, thus a given user will have MSO-specific information regarding its identity (such as login information, GUID, etc.) and is able to perform a single sign on to request and receive content.

RELATED APPLICATIONS

This application is related to co-owned, co-pending U.S. patentapplication Ser. No. 12/536,724 filed on Aug. 6, 2009 and entitled“SYSTEM AND METHOD FOR MANAGING ENTITLEMENTS TO DATA OVER A NETWORK”,co-owned U.S. Provisional Application Ser. No. 61/256,903 filed on Oct.30, 2009 and entitled “METHODS AND APPARATUS FOR PACKETIZED CONTENTDELIVERY OVER A CONTENT DELIVERY NETWORK”, and to co-owned, co-pendingU.S. patent application Ser. No. 12/______ filed concurrently herewithand entitled “APPARATUS AND METHODS FOR CONTENT DELIVERY AND MESSAGEEXCHANGE ACROSS MULTIPLE CONTENT DELIVERY NETWORKS”, each of which isincorporated herein by reference in its entirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND OF THE INVENTION

1. Field of Invention

The present invention relates generally to the field of content and/ordata delivery over one or more networks. More particularly, the presentinvention is related in one exemplary aspect to apparatus and methodsfor linking subscriber accounts across two or more networks for thedelivery of content across these networks.

2. Description of Related Technology

Recent advances in digital information processing and technology havemade a whole range of services and functions available for delivery toconsumers at various types devices for very reasonable prices orsubscription fees. These services and functions include digital contentor programming (movies, etc.), digital video-on-demand (VOD), personalvideo recorder (PVR) and networked PVR (nPVR), Internet Protocoltelevision (IPTV), digital media playback and recording, as well highspeed Internet access (including so-called “Internet TV”, wheretelevision programming is delivered over the Internet without QoS) andIP-based telephony (e.g., VoIP). Other services available to networkusers include access to, and recording of, digital music (e.g., MP3files).

Currently, many of these services are provided to the user via a widevariety of different equipment environments and delivery paradigmsincluding, inter alia, cable or satellite modems or QAMs, HFCu (i.e.,Hybrid Fiber-copper distribution via indigenous POST/PSTN and/or coaxialwiring in a premises), optical fiber such as FTTC, FTTH, etc., Wi-Fi™hubs, Ethernet hubs, gateways, switches, and routers, to a plurality ofuser equipment types. For example, content may be delivered to users atset-top boxes, personal (desktop) computers, laptop computers, othermini-computers (such as so-called “netbooks”, mini-notebook computers),and/or other devices. Recent advances in consumer electronics have alsoled to the widespread introduction of a variety of portable mediadevices (PMDs) such as, inter alia, portable digital music devices andother so-called “MP3 players”, cellular telephones/smartphones, handheldcomputers, and personal digital assistants (PDA), which allow users tostore and playback audio and video files. Furthermore, many users todaywish to view at least some content via the Internet and their mobiledevice.

Although a myriad of services, equipment, data formats and providers areavailable, current systems offer no mechanism for a managed networkoperator (e.g., MSO) to partner with service providers in order to allowusers who are verified as subscribers of the MSO network to obtain andutilize content from the network (such as via a subscription,pay-per-view, etc.), and to be able to view this content via theInternet or another such external network or internetwork via partneredservice provider websites or similar portals.

Another mechanism for providing video content to mobile devices is theForward Link Only (FLO), such as that offered by Qualcomm Corporation asthe MediaFLO® technology (also termed “FLO TV”). MediaFLO enables live,real time audio and video streams, as well as broadcast and scheduledvideo and audio clips and shows to be transmitted to the user's mobiledevice. The data transmission path in the MediaFLO system is one-way,from the tower to the device; there is no upstream communication. Hence,the MediaFLO system is not capable of providing enhanced features suchas trick mode operations (fast-forward, rewind, pause, so called “startover”, etc.) and/or advanced user interaction data collection. MediaFLOis also unable to provide premium or pay content, and instead hassomewhat limited content offerings. Further, the MediaFLO system doesnot provide on-demand capabilities, but rather only provides broadcast(or live) and scheduled video.

Hence, methods and apparatus are needed which enable a partnered serviceprovider to, pursuant to an on-demand or other request for protectedcontent, autonomously or non-autonomously determine if an identifiedprospective viewer of Internet content already subscribes or otherwisehas access rights to this content through the MSO, and if so provide thecontent (e.g., according to one or more delivery models associated withthe user's subscription or use rights). Ideally, the aforementionedmethods and apparatus would enable such content delivery while affordingminimal user input, such as via a single sign-on mechanism which allowsthe user to log in once and have his/her accounts with both the serviceprovider and the MSO linked. Ideally, the MSO subscriber may be providedwith additional types/delivery modes of content (e.g., broadcast,on-demand, pay-per-view, premium, etc.), and/or be provided with contentacross different delivery platforms via the Internet according to thesubscriber's service plan with the MSO. Such methods and apparatus wouldadvantageously enable a user to receive these various types of contenton any device and via any delivery paradigm (and not necessarilyaccording to a fixed schedule), thereby enhancing the user experience.

SUMMARY OF THE INVENTION

The present invention addresses the foregoing needs by disclosingapparatus and methods for content management and account linking acrossentities of two or more networks.

In a first aspect of the invention, a method for providing protectedcontent via a first network to a user of a second network is disclosed.In one embodiment, the method comprises: receiving at an entity of thesecond network a request for the protected content, the requestcomprising at least information identifying a requesting user andinformation identifying requested content; determining, based at leastin part on the information identifying the requesting user, an identityof the requesting user as an authorized user of the second network;generating a unique identifier for the authorized user; and transmittinga response to the request to an entity of the first network, theresponse comprising the unique identifier.

The transmission of the response may in one variant, be configured tocause the entity of the first network to deliver the protected contentto the authorized user. In another variant, the unique identifier isstored at the entity of the first network and is configured to enableuse in a subsequent request, the subsequent request comprising a requestfor second protected content different than the first content.

In a second aspect of the invention, an apparatus in a content deliverynetwork configured to authorize access to a selected one or moreservices at a packet network by at least one user device is disclosed.In one embodiment, the apparatus comprises: a first interface configuredto receive: information identifying the at least one user device and arequest for the access to the selected one or more services; a processorcomprising at least one computer program, the computer programconfigured to: verify the information identifying the at least one userdevice as being associated with at least one subscriber of the contentdelivery network, generate a unique identifier specific to thesubscriber, and generate a response to the request for the access to theselected one or more services; and a second interface configured totransmit: the unique identifier to at least one entity of the packetnetwork for storage thereon, and the response to the request for theaccess to the selected one or more services.

In a third aspect of the invention, a method for providing protectedcontent via a first content delivery network to an authorized user of asecond content delivery network is disclosed. In one embodiment, themethod comprises: receiving at an entity of the first network a requestfor the protected content from a user device, the request comprising atleast information identifying the user device and informationidentifying the protected content; querying a plurality of records todetermine a unique identifier of the user device, the unique identifierbeing previously provided by the second network; transmitting the uniqueidentifier and the information identifying the protected content to anentity of the second network; receiving in response to the transmissionof the unique identifier and the information identifying the protectedcontent, a response from the entity of the second network; anddelivering the protected content to the user device based at least inpart on the response.

In a fourth aspect of the invention, a method of operating a packetnetwork is disclosed. In one embodiment, the method comprises receivingfrom an IP-enabled device a request for content at an entity of thepacket network, the content being protected in accordance with one ormore policies specified by the operator of a managed contentdistribution network. The request comprises information uniquelyassociated with a subscriber of the managed network. Information storedat the entity received from the operator is accessed, the storedinformation enabling the entity to determine whether the request forcontent should be granted. When granting the request, a communication isissued to the managed network indicating that the content is beingprovided, and the content is provided to the requesting IP-enableddevice over the packet network, the content being at least partlyencapsulated using an IP protocol.

In an fifth aspect of the invention, a business and operation “rules”engine is disclosed. In one embodiment, the engine comprises one or morecomputer programs adapted to control various aspects of content andmessage exchange between two entities so as to achieve desired businessor operation goals (or obey certain rules). Business methods based one.g., the foregoing rules and content/message exchange are alsodisclosed.

In a sixth aspect of the invention, a computer-readable apparatus isdisclosed. In one embodiment, the apparatus comprises a storage devicehaving at least one program stored thereon, the program, when executed,facilitates providing protected content to subscribers of a managed(e.g., MSO) network via a content source accessible to the subscribervia the Internet or another external network.

These and other aspects of the invention shall become apparent whenconsidered in light of the disclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating an exemplary hybridfiber network configuration useful with the present invention.

FIG. 1 a is a functional block diagram illustrating one exemplarynetwork headend configuration useful with the present invention.

FIG. 1 b is a functional block diagram illustrating one exemplary localservice node configuration useful with the present invention.

FIG. 1 c is a functional block diagram illustrating one exemplarypacketized content delivery network architecture useful with the presentinvention.

FIG. 2 is a functional block diagram illustrating a content deliverynetwork architecture configured in accordance with one embodiment of thepresent invention.

FIG. 2 a is a functional block diagram illustrating a first exemplaryuse case of the content delivery network architecture of FIG. 2.

FIG. 2 b is a functional block diagram illustrating a second exemplaryuse case of the content delivery network architecture of FIG. 2.

FIG. 2 c is a functional block diagram illustrating a third exemplaryuse case of the content delivery network architecture of FIG. 2.

FIG. 3 is a logical flow diagram illustrating an exemplary method forproviding content delivery across one or more content delivery networksaccording to the present invention.

FIG. 4 is a diagram illustrating an exemplary communication flow forproviding content delivery across one or more content delivery networksaccording to the present invention.

FIG. 5 is a logical flow diagram illustrating an exemplary method forlinking subscriber accounts across one or more content delivery networksaccording to the present invention.

FIG. 6 is a diagram illustrating an exemplary communication flow forlinking subscriber accounts across one or more content delivery networksaccording to the present invention.

FIG. 7 is a logical flow diagram illustrating an exemplary method forunlinking a subscriber account according to the present invention.

FIG. 8 is a diagram illustrating an exemplary communication flow forunlinking a subscriber account according to the present invention.

FIG. 9 is a logical flow diagram illustrating an exemplary method forending a content delivery session facilitated via one or more contentdelivery networks according to the present invention.

FIG. 10 is a diagram illustrating an exemplary communication flow forending a content delivery session facilitated via one or more contentdelivery networks according to the present invention.

FIG. 11 is a logical flow diagram illustrating an exemplary method forterminating a session startup facilitated via one or more contentdelivery networks according to the present invention.

FIG. 12 is a diagram illustrating an exemplary communication flow forending a content delivery session facilitated via one or more contentdelivery networks according to the present invention.

All Figures© Copyright 2010 Time Warner Cable, Inc. All rights reserved.

DETAILED DESCRIPTION OF THE INVENTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “application” refers generally to a unit ofexecutable software that implements a certain functionality or theme.The themes of applications vary broadly across any number of disciplinesand functions (such as on-demand content management, e-commercetransactions, brokerage transactions, home entertainment, calculatoretc.), and one application may have more than one theme. The unit ofexecutable software generally runs in a predetermined environment; forexample, the unit could comprise a downloadable Java Xlet™ that runswithin the JavaTV™ environment.

As used herein, the terms “client device” and “end user device” include,but are not limited to, set-top boxes (e.g., DSTBs), personal computers(PCs), and minicomputers, whether desktop, laptop, or otherwise, andmobile devices such as handheld computers, PDAs, personal media devices(PMDs), and smartphones.

As used herein, the term “codec” refers to a video, audio, or other datacoding and/or decoding algorithm, process or apparatus including,without limitation, those of the MPEG (e.g., MPEG-1, MPEG-2,MPEG-4/H.264, etc.), Real (RealVideo, etc.), AC-3 (audio), DiVX,XViD/ViDX, Windows Media Video (e.g., WMV 7, 8, 9, 10, or 11), ATI Videocodec, or VC-1 (SMPTE standard 421M) families.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.) and the like.

The terms “Customer Premises Equipment (CPE)” and “host device” refer toany type of electronic equipment located within a customer's or user'spremises and connected to a network. The term “host device” refersgenerally to a terminal device that has access to digital televisioncontent via a satellite, cable, or terrestrial network.

As used herein, the term “display” means any type of device adapted todisplay information, including without limitation CRTs, LCDs, TFTs,plasma displays, LEDs, incandescent and fluorescent devices, orcombinations/integrations thereof. Display devices may also include lessdynamic devices such as, for example, printers, e-ink devices, and thelike.

As used herein, the term “DOCSIS” refers to any of the existing orplanned variants of the Data Over Cable Services InterfaceSpecification, including for example DOCSIS versions 1.0, 1.1, 2.0 and3.0. DOCSIS (version 1.0) is a standard and protocol for internet accessusing a “digital” cable network.

As used herein, the term “headend” refers generally to a networkedsystem controlled by an operator (e.g., an MSO) that distributesprogramming to MSO clientele using client devices. Such programming mayinclude literally any information source/receiver including, inter alia,free-to-air TV channels, pay TV channels, interactive TV, and theInternet.

As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet.

As used herein, the terms “microprocessor” and “digital processor” aremeant generally to include all types of digital processing devicesincluding, without limitation, digital signal processors (DSPs), reducedinstruction set computers (RISC), general-purpose (CISC) processors,microprocessors, gate arrays (e.g., FPGAs), PLDs, reconfigurable computefabrics (RCFs), array processors, and application-specific integratedcircuits (ASICs). Such digital processors may be contained on a singleunitary IC die, or distributed across multiple components. As usedherein, the terms “MSO” or “multiple systems operator” refer to a cable,satellite, or terrestrial network provider having infrastructurerequired to deliver services including programming and data over thosemediums.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (BIC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications or networking protocols(e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP,3GPP2, WAP, SIP, UDP, FTP, RTP/RTCP, H.323, etc.).

As used herein, the term “network interface” refers to any signal ordata interface with a component or network including, withoutlimitation, those of the FireWire (e.g., FW400, FW800, etc.), USB (e.g.,USB2), Ethernet (e.g., 10/100, 10/100/1000 (Gigabit Ethernet), 10-Gig-E,etc.), MoCA, Coaxsys (e.g., TVnet™), radio frequency tuner (e.g.,in-band or OOB, cable modem, etc.), Wi-Fi (802.11a,b,g,n), WiMAX(802.16), PAN (e.g., 802.15), or IrDA families.

As used herein, the term “QAM” refers to modulation schemes used forsending signals over cable networks. Such modulation scheme might useany constellation level (e.g. QPSK, 16-QAM, 64-QAM, 256-QAM, etc.)depending on details of a cable network. A QAM may also refer to aphysical channel modulated according to the schemes.

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “storage device” refers to without limitationcomputer hard drives, DVR device, memory, RAID devices or arrays,optical media (e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any otherdevices or media capable of storing content or other information.

As used herein, the term “Wi-Fi” refers to, without limitation, any ofthe variants of IEEE-Std. 802.11 or related standards including 802.11a/b/g/n/v.

As used herein, the term “wireless” means any wireless signal, data,communication, or other interface including without limitation Wi-Fi,Bluetooth, 3G, HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A, WCDMA, etc.),FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20, narrowband/FDMA,OFDM, PCS/DCS, analog cellular, CDPD, satellite systems, millimeter waveor microwave systems, acoustic, and infrared (i.e., IrDA).

Overview

The present invention discloses, inter glia, methods and apparatus forproviding protected content to subscribers of a managed (e.g., MSO)network via a content source accessible to the subscriber via theInternet or another external network. In one embodiment, a user accessesa third party service provider (content source) website, and requestsdelivery of content (e.g., via on-demand type streaming, broadcast, highspeed file download, etc.). If the particular content requested isprotected content or content which is only accessible to certain typesof subscribers, the service provider and/or MSO determines whether therequesting user is permitted to access the content. The process by whichit is determined whether a user may access content includes (i)authenticating the user as a subscriber to the MSO, and (ii) determiningwhether the subscriber's service/subscription level permits viewing ofthe requested content (and optionally one or more use restrictions). Theprocess is advantageously agnostic to the underlying networks involvedin both the request and content delivery processes.

In one variant, the user is authenticated by requiring him/her toestablish a login identity and password, and/or assigning the user aGUID. The user's MAC address or IP address may also be used in thisprocess. This unique information is stored at an MSO entity, and whenthe user requests content, the user must log into the MSO; the relevantinformation is retrieved and compared to information that the user hasprovided in their login. If valid login information is entered (i.e.,the information provided matches the stored information for that userGUID), then a session is created between the MSO and user.

The aforementioned authentication at the MSO may be facilitated byvarious entities associated with the service provider. For instance, theuser may first log in to a service provider's website, such as byestablishing a login identity and password which are stored at theservice provider's site. Once logged in, the service provider mayforward requests to view content to an appropriate MSO and provide aplatform for the user to log in to the MSO site.

In another variant, the service provider and MSO accounts for aparticular user may be linked or federated. In other words, a trustrelationship is established between the service provider and MSO, whichis used to verify subscriber information. According to this embodiment,a given user will have MSO-specific information regarding its identity(such as login information for the MSO, GUID, etc.), and/or informationregarding its subscription level and other service details stored at theservice provider site. Messages received from the MSO representingpermission for the user to access content may also be stored at theservice provider site. The service provider may later reference thisinformation when subsequent requests for content are made by the userfor content, thereby providing faster and more efficient service.

Methods for unlinking or de-federating a user's account in the serviceprovider and MSO sites are also disclosed.

In other variants, the MSO enables the service provider to enforcesecurity or rights management protection (e.g., DRM, encryption keys,etc.) on content authorized for delivery, such as by pre-positioninginformation enabling this protection (and specific to the requestingsubscriber) at the service provider.

Similarly, another variant disclosed allows the service provider topre-configure the requested content based on one or more configurationparameters associated with the requesting device (e.g., codec support,DRM support, display capabilities, etc.).

Business rules for the implementation of the aforementioned methods andfor the delivery of content are also disclosed.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Exemplary embodiments of the apparatus and methods of the presentinvention are now described in detail. While these exemplary embodimentsare described in the context of use with the aforementioned hybrid fibercoax (HFC) cable system, or satellite network architecture having anmultiple systems operator (MSO), digital networking capability, IPdelivery capability, and plurality of client devices/CPE, the generalprinciples and advantages of the invention may be extended to othertypes of networks and architectures, whether broadband, narrowband,wired or wireless, or otherwise, the following therefore being merelyexemplary in nature. For instance, the invention may be adapted for useon so-called hybrid fiber copper (HFCu) networks, or WiMAX (IEEE Std.802.16) wireless networks.

It will also be appreciated that while described generally in thecontext of a consumer (i.e., home) end user domain, the presentinvention may be readily adapted to other types of environments (e.g.,commercial/enterprise, government/military, etc.) as well. Myriad otherapplications are possible.

Also, while certain aspects are described primarily in the context ofthe well-known Internet Protocol (described in, inter alia, RFC 791 and2460) and Session Initiation Protocol (SIP), it will be appreciated thatthe present invention may utilize other types of protocols (and in factbearer networks to include other internets and intranets) to implementthe described functionality.

Other features and advantages of the present invention will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

Network—

FIG. 1 illustrates a typical content delivery network configuration withwhich the apparatus and methods of the present invention may be used.The various components of the network 100 include (i) one or more dataand application origination points 102; (ii) one or more content sources103, (iii) one or more application distribution servers 104; (iv) one ormore VOD servers 105, and (v) customer premises equipment (CPE) 106. Thedistribution server(s) 104, VOD servers 105 and CPE(s) 106 are connectedvia a bearer (e.g., HFC) network 101. The headend is also connectedthrough a gateway or other such interface (not shown) to unmanagedexternal internetworks such as the Internet 111. A simple architecturecomprising one of each of the aforementioned components 102, 104, 105,106 is shown in FIG. 1 for simplicity, although it will be recognizedthat comparable architectures with multiple origination points,distribution servers, VOD servers, and/or CPE devices (as well asdifferent network topologies) may be utilized consistent with theinvention. For example, the headend architecture of FIG. 1 a (describedin greater detail below) may be used.

The data/application origination point 102 comprises any medium thatallows data and/or applications (such as a VOD-based or “Watch TV”application) to be transferred to a distribution server 104. This caninclude for example a third party data source, application vendorwebsite, CD-ROM, external network interface, mass storage device (e.g.,RAID system), etc. Such transference may be automatic, initiated uponthe occurrence of one or more specified events (such as the receipt of arequest packet or ACK), performed manually, or accomplished in anynumber of other modes readily recognized by those of ordinary skill.

The application distribution server 104 comprises a computer systemwhere such applications can enter the network system. Distributionservers are well known in the networking arts, and accordingly notdescribed further herein.

The VOD server 105 comprises a computer system where on-demand contentcan be received from one or more of the aforementioned data sources 102and enter the network system. These servers may generate the contentlocally, or alternatively act as a gateway or intermediary from adistant source.

The CPE 106 includes any equipment in the “customers' premises” (orother locations, whether local or remote to the distribution server 104)that can be accessed by a distribution server 104.

Referring now to FIG. 1 a, one exemplary embodiment of a headendarchitecture useful with the present invention is described. As shown inFIG. 1 a, the headend architecture 150 comprises typical headendcomponents and services including billing module 152, subscribermanagement system (SMS) and CPE configuration management module 154,cable-modem termination system (CMTS) and OOB system 156, as well asLAN(s) 158, 160 placing the various components in data communicationwith one another. It will be appreciated that while a bar or bus LANtopology is illustrated, any number of other arrangements as previouslyreferenced (e.g., ring, star, etc.) may be used consistent with theinvention. It will also be appreciated that the headend configurationdepicted in FIG. 1 a is high-level, conceptual architecture and thateach MSO may have multiple headends deployed using custom architectures.

The exemplary architecture 150 of FIG. 1 a further includes amultiplexer-encrypter-modulator (MEM) 162 coupled to the HFC network 101adapted to process or condition content for transmission over thenetwork. The distribution servers 164 are coupled to the LAN 160, whichprovides access to the MEM 162 and network 101 via one or more fileservers 170. The VOD servers 105 are coupled to the LAN 160 as well,although other architectures may be employed (such as for example wherethe VOD servers are associated with a core switching device such as an802.3z Gigabit Ethernet device). As previously described, information iscarried across multiple channels. Thus, the headend must be adapted toacquire the information for the carried channels from various sources.Typically, the channels being delivered from the headend 150 to the CPE106 (“downstream”) are multiplexed together in the headend, aspreviously described and sent to neighborhood hubs (FIG. 1 b) via avariety of interposed network components.

It will also be recognized, however, that the multiplexing operation(s)need not necessarily occur at the headend 150 (e.g., in theaforementioned MEM 162). As one alternative, a multi-location ormulti-stage approach can be used, such as that described in U.S. Pat.No. 7,602,820, entitled “APPARATUS AND METHODS FOR MULTI-STAGEMULTIPLEXING IN A NETWORK” incorporated herein by reference in itsentirety, which discloses inter glia improved multiplexing apparatus andmethods that allow such systems to dynamically compensate for content(e.g., advertisements, promotions, or other programs) that is insertedat a downstream network node such as a local hub, as well as “feed-back”and “feed forward” mechanisms for transferring information betweenmultiplexing stages.

Content (e.g., audio, video, data, files, etc.) is provided in eachdownstream (in-band) channel associated with the relevant service group.To communicate with the headend or intermediary node (e.g., hub server),the CPE 106 may use the out-of-band (OOB) or DOCSIS channels andassociated protocols. The OCAP 1.0 (and subsequent) specificationprovides for exemplary networking protocols both downstream andupstream, although the invention is in no way limited to theseapproaches.

It will also be recognized that the multiple servers (broadcast, VOD, orotherwise) can be used, and disposed at two or more different locationsif desired, such as being part of different server “farms”. Thesemultiple servers can be used to feed one service group, or alternativelydifferent service groups. In a simple architecture, a single server isused to feed one or more service groups. In another variant, multipleservers located at the same location are used to feed one or moreservice groups. In yet another variant, multiple servers disposed atdifferent location are used to feed one or more service groups.

An optical transport ring (not shown) is also commonly utilized todistribute the dense wave-division multiplexed (DWDM) optical signals toeach hub within the network in an efficient fashion.

In addition to on-demand and broadcast content (e.g., videoprogramming), the system of FIGS. 1 a and 1 b (and 1 c discussed below)also deliver Internet 111 data services using the Internet protocol(IP), although other protocols and transport mechanisms of the type wellknown in the digital communication art may be substituted. One exemplarydelivery paradigm comprises delivering MPEG-based video content, withthe video transported to user PCs (or IP-based STSs) over theaforementioned DOCSIS channels comprising MPEG (or other video codecsuch as H.264 or AVC) over IP over MPEG. That is, the higher layer MPEG-or other encoded content is encapsulated using an IP protocol, whichthen utilizes an MPEG packetization of the type well known in the artfor delivery over the RF channels, such as via a multiplexed transportstream (MPTS). In this fashion, a parallel delivery mode to the normalbroadcast delivery exists; i.e., delivery of video content both overtraditional downstream QAMs to the tuner of the user's STB or otherreceiver device for viewing on the television, and also as packetized IPdata over the DOCSIS QAMs to the user's PC or other IP-enabled devicevia the user's cable modem. Delivery in such packetized modes may beunicast, multicast, or broadcast. Delivery of the IP-encapsulated datamay also occur over the non-DOCSIS QAMs, such as described below withrespect to FIG. 1 c.

The CPE 106 are each configured to monitor the particular assigned RFchannel (such as via a port or socket ID/address, or other suchmechanism) for TP packets intended for the subscriber premises/addressthat they serve.

While the foregoing network architectures described herein can (and infact do) carry packetized content (e.g., IP over MPEG for high-speeddata or Internet TV, MPEG2 packet content over QAM for MPTS, etc.), theyare often not optimized for such delivery. Hence, in accordance withanother embodiment of the present invention, a “packet optimized”delivery network is used for carriage of the packet content (e.g., IPTVcontent) when the request issues from an MSO network (see discussion ofFIG. 2 a below). FIG. 1 c illustrates one exemplary implementation ofsuch a network, in the context of an IMS (IP Multimedia Subsystem)network with common control plane and service delivery platform (SDP),as described in co-pending U.S. Provisional Patent Application Ser. No.61/256,903 entitled “METHODS AND APPARATUS FOR PACKETIZED CONTENTDELIVERY OVER A CONTENT DELIVERY NETWORK”, previously incorporatedherein. Such a network provides significant enhancements in terms ofcommon control of different services, implementation and management ofcontent delivery sessions according to unicast or multicast models,quality-of-service (QoS) for IP-packetized content streams, etc.;however, it is appreciated that the various features of the presentinvention are in no way limited to any of the foregoing architectures.

Content Delivery Network Architecture—

The approach to providing access to protected content outside of an MSOnetwork described in the present disclosure are based in the exemplaryembodiment on a pre-defined set of transactions or assertions which arepassed between the content provider (e.g., service provider or otherthird-party entity) and the managed network operator (e.g., MSO). Theassertions are conducted between applications proprietary to both of theaforementioned organizations, yet externalized through a set ofstandards-based protocols. In one implementation of the invention, theprotocols utilized include those defined by the Liberty AllianceProject, and/or by the Organization for the Advancement of StructuredInformation Standards (OASIS), although it will be recognized that otherprotocols may be used with equal success.

The Liberty Alliance, formed in 2001, created a set of open standardsand guidelines for identity management with the fundamental concept of“identity federation” (or the linking of accounts within or acrossdisparate organizations). The guidelines produced from the project,known as Liberty Alliance Identity Federation Framework (ID-FF) V1.2specification, which is incorporated herein by reference in itsentirety, define the process by which identities from trusted sourcescan be linked in order to reduce ongoing multiple logins, thusincreasing identity assurance while reducing identity fraud. In 2003,the Liberty Alliance contributed their body of work to OASIS that wasfounded in 1993 under the name SGML Open. SGML Open's original charterwas the creation of guidelines for interoperability among productssupporting the Standard Generalized Markup Language (SGML), but in 1998SGML Open changed its name and shifted its focus from SGML to ExtensibleMarkup Language (XML), as it became widely adopted by the technologyindustry.

To date, specifications from OASIS have become the de facto standard forsecurity and identification management between consenting businesspartners, which is represented through the Security Assertion Markuplanguage (SAML) Specification (Version 2.0 released in 2005), which isincorporated herein by reference in its entirety. Early versions of SAMLand the ID-FF were compatible; however, the two standards becameincompatible based on component changes within SAML for greaterconsistency and component symmetry. Other key differences addressed inSAML v2.0 were encryption metadata and multi-endpoint support for asingle protocol. Also, SAML v2.0 generalized the Liberty functionalityto account for more options or use cases for expanded definition.However, it will be appreciated that the present invention is notlimited to any particular standards or languages, the foregoing SAML andID-FF being merely exemplary of the broader principles of the invention.

Referring now to FIG. 2, a high-level block diagram of a contentdelivery network architecture 200 configured in accordance with oneembodiment of the invention and for use in providing delivery ofprotected content to so-called “entitled” viewers is illustrated. Asdiscussed herein, the network architecture 200 generally provides accessto protected content outside of an MSO 201 network (e.g., via a serviceprovider 202) to subscribers. The network 200 generally comprises one ormore service providers 202, an MSO 202 and a plurality of clientdevices, such as CPE 106 and portable media device (PMD) 107.

The service providers 202 may for example include any broadcast provider(such as e.g., NBC, Turner Broadcasting, Viacom, etc.) which distributescontent across one or more mediums, or through distribution agreementswith the MSO 201. Subscribers include the individual consumers or usersof video/audio/data services.

Subscribers request access to content via user devices such as e.g.,consumer premises equipment (CPE) 106, personal media devices (PMD) 107,personal computers (PC), laptop computers, mobile devices, etc. The userdevices may include any apparatus capable receiving audio/video/dataservices from the MSO 201 or service provider 202 via the Internet.Hence, two primary request/delivery models are envisaged (althoughothers may be used as well, or combinations or variants of theforegoing): (i) request from an MSO-network device (e.g., CPE 106 suchas an IP-enabled DSTB or premises gateway 113) to an Internet site (suchas e.g., the external web application 204), for content to be returnedback to the requesting MSO-network device (see FIG. 2 a); and (ii)request from a non-MSO network device, for content to be returned backto the requesting non-MSO network device (see FIG. 2 b).

An example of the former case (i) might be an IP-enabled DSTB orPC/DOCSIS cable modem registered with the MSO 201 that utilizes MSOinfrastructure to access the Internet (and the third party serviceprovider/source site), with content being streamed back to therequesting device over a comparable pathway. Here, the MSO network actsboth as a “bearer” and “authorizer” network. Note that in oneembodiment, although the subscriber is using (primarily) MSOinfrastructure and requesting MSO protected content, the source of thecontent is actually a third party (e.g., web server), and hence thecontent is delivered in an essentially agnostic fashion (i.e., the MSOdoes not know that it is carrying its own content, but rather theprotected content appears to be just any other third party content (andhence advantageously does not require any special routing, management,or other considerations).

An example of the latter case (ii) might be an IP-enabled mobile device(e.g., smartphone or laptop computer) which may or may not be registeredwith the MSO 201, and is being operated by an authorized MSO subscriber.The device may obtain access to the Internet via e.g., a serviceprovider WLAN, cellular 3G/4G (e.g., LTE-A), WiMAX, or other suchinterface 250, whereby it may connect to the third party website andrequest content, the latter streamed to the device over a comparablereturn path when delivery is authorized. In this fashion, the MSO 201network is not a bearer, but rather merely an authorizer.

FIG. 2 c illustrates yet another use case of the content delivery andmessage exchange network architecture of FIG. 2, wherein an MSO-operated(or “federated”) site is used.

The flow of various communications (and the protected content) under theforegoing exemplary scenarios are also illustrated in FIGS. 2 a-2 c,respectively. In various models, the subscriber request is received at:(i) the external web application 204 or third party server; and/or (ii)an MSO-maintained website. The subscriber (and/or device) requestingaccess to content is authenticated, and its authorization to receive thecontent is validated by an entitlement server 208 and identity provider210; additional entities may be utilized as well. This authenticationand authorization may take many forms, such as those describedsubsequently herein (e.g., authentication of the user and/or theirdevice, authorization of the user to access content, etc.), as well asthose discussed in previously referenced, co-owned, co-pending U.S.patent application Ser. No. 12/______ filed concurrently herewith andentitled “APPARATUS AND METHODS FOR CONTENT DELIVERY AND MESSAGEEXCHANGE ACROSS MULTIPLE CONTENT DELIVERY NETWORKS”. Alternatively, IEEEStd. 802.1x authentication, a RADIUS server, etc. of the type well knownin the networking arts may be utilized for authentication and/orauthorization.

Once the subscriber (and/or device) is authenticated and authorized, thecontent may be provided from the service provider content server 206 tothe requesting device (e.g., CPE 106, PMD 107, etc.). The serviceprovider may also designate a proxy to deliver the content (e.g., afourth party with which the third party service provider has an existingrelationship).

As indicated, before the protected content may be provided thereto (viathe content server 206), the service provider 202 must authenticate therequesting device as being an MSO 201 subscriber and ensure therequesting subscriber is authorized to view the requested content. Theauthentication step (determining whether the requesting user is an MSO201 subscriber) utilizes at least an MSO-based identity provider 210.The authorization step (determining the “entitlements” of the subscriberwith respect to the requested content) utilizes at least an MSO-basedentitlements server 208.

Two exemplary models by which a user's status as an MSO subscriber isauthenticated are discussed herein, although other paradigms will beappreciated by those of ordinary skill given the present disclosure. Thefirst model enables “linking” of the service provider's 202 subscriberidentity to the MSO's 201 subscriber identity. This link allows theservice 202 to avoid having to redirect the subscriber back to the MSO201 for authentication once the accounts have been linked. The secondmethod (“non-linking”) is used in the event the service provider 202does not maintain identities for its subscribers, and instead leveragesonly the MSO 201 identity provider 210 for authentication; i.e., if theservice provider 202 does not support its own identity management system(IDMS). In one variant, the non-linked embodiment requires that theservice provider 202 enforce an MSO 201 policy that authentications aresession-based and cannot be persistent.

In one embodiment, the architecture 200 for providing delivery ofprotected content outside an MSO 201 network may include the componentsdiscussed in co-owned, co-pending U.S. patent application Ser. No.12/______ and entitled “APPARATUS AND METHODS FOR CONTENT DELIVERY ANDMESSAGE EXCHANGE ACROSS MULTIPLE CONTENT DELIVERY NETWORKS” which waspreviously incorporated herein by reference in its entirety.

As noted above, the requested/provided content may comprise traditionalbroadcast content as well as on-demand content. Other types of contentmay also be provided. For example, so called “quick clips” content(described in co-owned U.S. Pat. No. 7,174,126 issued Feb. 6, 2007 andentitled “TECHNIQUE FOR EFFECTIVELY ACCESSING PROGRAMMING LISTINGINFORMATION IN AN ENTERTAINMENT DELIVERY SYSTEM” incorporated herein byreference in its entirety), so-called “start-over” content (described inco-owned, co-pending U.S. Patent Publication No. 2005/0034171 entitled“TECHNIQUE FOR DELIVERING PROGRAMMING CONTENT BASED ON A MODIFIEDNETWORK PERSONAL VIDEO RECORDER SERVICE” incorporated herein byreference in its entirety), so-called “lookback” content (as describedin co-owned, co-pending U.S. patent application Ser. No. 10/913,064filed Aug. 6, 2004 and entitled “TECHNIQUE FOR DELIVERING PROGRAMMINGCONTENT BASED ON A MODIFIED NETWORK PERSONAL VIDEO RECORDER SERVICE”incorporated herein by reference in its entirety), and/or so-called“remote DVR” content (as discussed in co-owned U.S. Pat. No. 7,457,520issued Nov. 25, 2008 and entitled “TECHNIQUE FOR PROVIDING A VIRTUALDIGITAL VIDEO RECORDER SERVICE THROUGH A COMMUNICATIONS NETWORK”incorporated herein by reference in its entirety) may be delivered.Still further, enhanced access to premium based content which is notavailable to non-subscribers, or which cannot be delivered acrosstraditional transport may also be provided, such as e.g., behind thescenes outtakes, alternate endings, actor interviews, etc.

As will be discussed in greater detail below, the aforementioned networkarchitecture further enables upstream communication between the userdevices (CPE 106 and/or PMD 107) and service provider 202 and MSO 201.Accordingly, entities at the service provider 202 and/or MSO 201 maycollect usage data from the devices (whether actively via upstreammessages or signaling, or passively based on user request/trick mode orother types of behavior), as well as provide the user with trick modecapabilities with respect to the content (e.g., fast forward, rewind,pause, etc.) where applicable.

Delivery of content to the CPE 106 and/or PMD 107 occurs within the MSOnetwork (i.e., under the paradigm of FIG. 2 a) in one embodiment, asdiscussed in previously incorporated co-owned U.S. ProvisionalApplication Ser. No. 61/256,903 filed on Oct. 30, 2009 and entitled“METHODS AND APPARATUS FOR PACKETIZED CONTENT DELIVERY OVER A CONTENTDELIVERY NETWORK”. As discussed therein, a substantially session-basedand packetized content delivery approach (e.g., using the well-knownInternet Protocol) which allows for temporal, device, and locationflexibility in the delivery of the content, andtransportability/migration of user sessions (i.e., allows a user toreceive any content they desire, delivered at any time and at anylocation, and on any device they choose), as well as service/contentpersonalization (e.g., on a per-session/user basis) and blending(integration). This approach uses a common or unified deliveryarchitecture in providing what were heretofore heterogeneous servicessupplied by substantially different, and often vendor-specific,networks.

Moreover, the foregoing apparatus and methods provide for enhancedcontent access, reproduction, and distribution control (via e.g., aDRM-based approach and other security and content control measures), aswell as quality-of-service (QoS) guarantees which maintain high mediaquality and user experience, especially when compared to prior art“Internet TV” paradigms. In one exemplary implementation, the networkmay be based on an IMS (IP Multimedia System, such as e.g., that definedin relevant 3GPP standards) which includes SIP session protocols, aswell as a Service Delivery Platform (SDP).

In another implementation (FIG. 2 b), the network comprises both“managed” and “unmanaged” (or off-network) services, so that a networkoperator can utilize both its own and external infrastructure to providecontent delivery to its subscribers in various locations and use cases.

In one variant of this approach, network services are sent “over thetop” of other provider's infrastructure, thereby making the serviceprovider network substantially transparent (i.e., the protected contentrequests and other communications are passed over the service providernetwork and the Internet as if they are any other traffic). In anothervariant, a cooperative approach between providers is utilized, so thatfeatures or capabilities present in one service provider's network(e.g., authentication of mobile devices to an AP or RAN) can beleveraged by another provider operating in cooperation therewith.

In another embodiment, requested content may be authorized via thecontent and data distribution architecture 200, and provided to the CPE106 and/or PMD 107 as described in co-owned, co-pending U.S. patentapplication Ser. No. 11/258,229 filed on Oct. 24, 2005 and entitled“METHOD AND APPARATUS FOR ON-DEMAND CONTENT TRANSMISSION AND CONTROLOVER NETWORKS”, which is incorporated herein by reference in itsentirety. As discussed therein, data may be provided according todownload or “on-demand” paradigms. In one embodiment, the networkcomprises a cable television network connected with a CSP (cellularservice provider) or wireless service provider (WSP), and on-demandcontent delivery is accomplished via a “point-to-point” approach whereina session is established between a content receiving entity (such as acellular telephone) and a distributing entity (e.g., a VOD server).Session establishment and data flow control are advantageouslyimplemented using protocols and bandwidth that are typically used for(i) providing on-demand services to subscribers within the cablenetwork, and (ii) delivery and control of streaming multimedia to clientmobile devices.

Yet other mechanisms and architectures for providing content to PMDs 107and/or CPE 106 located in or out of a managed network may be usedconsistent with the invention as well, the foregoing being merelyexemplary of the broader principles.

As will be discussed in greater detail below, the architecture 200utilizes information obtained from or stored at an MSO-maintainedauthorization server (not shown) to determine whether a requesting userdevice is authorized to receive the content. In one embodiment, theprovision of content and use thereof are effectively controlled by thesupplying web or service provider content server 206 (or anyintermediary MSO-operated infrastructure). For example, once a user isauthorized to receive content, the server 206 serves the content to theuser device over the prescribed delivery path/model.

In another embodiment, various restrictions to the provision of contentto a user at a display device associated with the user device aredetermined by the device (e.g., CPE 106, PMD 107, etc.) itself, asdiscussed in co-owned, co-pending U.S. patent application Ser. No.12/716,131 filed on Mar. 2, 2010 and entitled “APPARATUS AND METHODS FORRIGHTS-MANAGED CONTENT AND DATA DELIVERY”, which is incorporated hereinby reference in its entirety. As discussed therein, a downloadable ortransferrable rights profile coupled with a “smart” media playerapplication are given. The rights profile contains information regardingthe specific rights of a device and/or a subscriber to access content.It is via the rights profile that the device (via the media player andits associated rights management application) determines whether toprovide content to a subscriber.

In one implementation of the architecture of FIGS. 2 a-2 c, one or moreentities useful in delivery of content to the CPE 106 or PMD 107 may beadapted to utilize information regarding the CPE 106 or PMD 107capabilities (e.g., such as in the event a capabilities profile isreceived from these devices) to performde-encapsulation/re-encapsulation of content where necessary, as isdisclosed in co-owned, co-pending U.S. patent application Ser. No.12/582,619 filed on Oct. 20, 2009 and entitled “GATEWAY APPARATUS ANDMETHODS FOR DIGITAL CONTENT DELIVERY IN A NETWORK”, which isincorporated herein by reference in its entirety. As discussed therein,one or more entities of the service provider 202 or MSO 201 (or locatedelsewhere) may be configured to process content includingde-encapsulating the content from a first media file container formatand subsequently re-encapsulating the content to a second media filecontainer format which is known to be compatible with the requestingdevice. For example, content which is delivered from a host server orother content source may be encapsulated in e.g., MP4, if the receivingCPE 106 is not capable of reading the MP4 files, the content server (orother entity) may re-encapsulate the content to e.g., MPEG-2 or toanother format that the receiving CPE 106 is capable of reading.

In another exemplary embodiment, the receiving device may comprise aconverged premises device (CPD) and/or a media bridge. The CPD may forexample be of the type described in co-owned and co-pending U.S. patentapplication Ser. No. 11/378,129 filed Mar. 16, 2006 and entitled“METHODS AND APPARATUS FOR CENTRALIZED CONTENT AND DATA DELIVERY”,incorporated herein by reference in its entirety. As discussed therein,the CPD comprises a WLAN (e.g., Wi-Fi) and/or PAN (e.g., Bluetooth or802.15) wireless interface. Packetized (e.g., IP) traffic may beexchanged between the CPD and a PMD 107 via, e.g. the WLAN/PANinterface. Hence, in one embodiment, the PMD 107 may request contentfrom the CPD.

In yet another embodiment, the user device may comprise a media bridge,which may, for example, be of the type disclosed in co-owned, co-pendingU.S. patent application Ser. No. 12/480,597 filed Jun. 8, 2009 andentitled “MEDIA BRIDGE APPARATUS AND METHODS”, incorporated herein byreference in its entirety. As discussed therein, the media bridgingapparatus acts as a connection between a PMD 107 (which may includee.g., an iPod™, handheld computer, smartphone, PDA, etc.) and a user'shome network. This bridging apparatus may be used, for example, toconvert content stored on the PMD 107 to a format capable of beingpresented on a user's set-top box or other client device. The bridgingapparatus may also be utilized for transmitting content to the PMD 107(such as by converting the content to a format capable of beingstored/presented on the PMD 107) provided the user of the PMD 107 isauthorized to receive the content.

As noted above, in one embodiment, the MSO 201 may utilize thecomponents discussed in co-owned, co-pending U.S. patent applicationSer. No. 12/______ and entitled “APPARATUS AND METHODS FOR CONTENTDELIVERY AND MESSAGE EXCHANGE ACROSS MULTIPLE CONTENT DELIVERY NETWORKS”including e.g., a technology services group (TSG) authorizationinfrastructure and an advance technology group (ATG) authenticationinfrastructure. As discussed therein, the authorization infrastructureand authentication infrastructure may comprise at least an MSO-basedcommon login application (CLA), a service oriented architecture (SOA),an enterprise identity system (EIS) and an identity provider. Theaforementioned infrastructures communicate with one or more serviceproviders 202 prior to enabling delivery therefrom of requested contentto a subscriber.

As shown in FIG. 2, the service provider 202 may further comprise astorage entity 212. In the event account federation is utilized, thestorage entity 212 may be used to store records relating to thesubscribers and/or the client devices. For example, the storage entity212 may store a user-specific global unique identifier (GUID) or otherinformation which may be used to recognize the subscriber within theservice provider 202 network and/or within the appropriate MSO 201.

Communication between the various entities of the network may, in oneembodiment, utilize the entitlements description language set forth inthe previously referenced co-owned, co-pending U.S. patent applicationSer. No. 12/______ and entitled “APPARATUS AND METHODS FOR CONTENTDELIVERY AND MESSAGE EXCHANGE ACROSS MULTIPLE CONTENT DELIVERYNETWORKS”.

Authentication Without Linked Accounts—

Referring now to FIG. 3, an exemplary method for authenticating a userwithout utilizing account linking or federation is illustrated. Asindicated above, the method of FIG. 3 is useful in the instance theservice provider 202 does not support any form of identity management(e.g., have an IDMS) and simply relies on the MSO 201 to handle thelogin process for access to protected content.

Per step 302 of the method, a request for access to protected content isreceived from the subscriber at the external node (e.g., web application204).

When the request is received, the service provider 202 forwards therequest to the MSO-based identity provider 210. In one embodiment, theservice provider 202 may format the request to comprise an ExtensibleHypertext Markup Language (XHTML) form which comprises a HypertextTransfer Protocol (HTTP) POST message that POSTs to the identityprovider server 210 containing the following elements:

SAMLRequest—containing a value of AuthnRequest

RelayState—optional

-   -   © Copyright 2010 Time Warner Cable, Inc. All rights reserved.

In one embodiment, the service provider 202 and identity provider 210use HTTP POST binding. An exemplary identity provider 210 POST URL maybe as follows:

http://ids.rr.com/nidp/sam12/sso

At step 306, the identity provider 210 determines whether a loginsession has been created. If the session exists, the content is providedto the user. In other words, as will be discussed in greater detailbelow, if the subscriber has already logged onto the MSO login page(and/or the user GUM has been stored at the service provider 202), theMSO will immediately be made aware of the user's credentials, and thatthe user is authorized to receive the content. If no login session hasbeen created, there is no security context for the subscriber, and thesubscriber is redirected to the MSO login page (step 308). At the loginpage, the subscriber logs-in using for example, a user identifier andpassword combination or other means for validating the subscriber'sdigital identity. Methods and apparatus for creating a digital identityare discussed in previously incorporated co-owned, co-pending U.S.patent application Ser. No. 12/______ entitled “APPARATUS AND METHODSFOR CONTENT DELIVERY AND MESSAGE EXCHANGE ACROSS MULTIPLE CONTENTDELIVERY NETWORKS”.

Per step 310, the login credentials are validated. If the enteredcredentials are not valid (e.g., do not match stored information for thesubscriber, and/or no stored information for the subscriber can befound), an error message is presented to the subscriber (step 312). Ifthe credentials are valid, the identity provider 210 returns a responseto the request at step 314.

In one embodiment, an XHTML form is returned to a browser which returnsthe following to the external service provider 202:

SAMLRepsonse—contains a value of Response type

RelayState—if provided in the initial request

-   -   © Copyright 2010 Time Warner Cable, Inc. All rights reserved.

Since the service provider 202 in the embodiment of FIG. 3 does notmaintain an IDMS, the subscriber must log into the MSO 201 (via theidentity provider 210) for every new web session.

Next, per step 316, in response to receiving the response, the serviceprovider 202 sends an authorization request to the MSO-based entitlementserver 208. In one embodiment, the entitlements server 208 may be of thetype discussed in previously incorporated U.S. patent application Ser.No. 12/536,724 filed on Aug. 6, 2009 and entitled “SYSTEM AND METHOD FORMANAGING ENTITLEMENTS TO DATA OVER A NETWORK”. In an alternativeembodiment, the entitlements server 208 may correspond in functionalityto the SOA and other entities of the authorization infrastructurediscussed in previously referenced U.S. patent application Ser. No.12/______ entitled “APPARATUS AND METHODS FOR CONTENT DELIVERY ANDMESSAGE EXCHANGE ACROSS MULTIPLE CONTENT DELIVERY NETWORKS”.

At step 318, a response to the authorization request is received. Theresponse reflects whether the service details for the particularsubscriber permit the subscriber to access the requested content. Forexample, if it is determined (at the entitlements server 208) that asubscriber is a so-called “basic” subscriber, and the request is forcontent which is classified as “premium” content, then the servicedetails for the subscriber do not permit the subscriber to access thecontent. When this occurs, the response to the authorization requestwill indicate a denial of service. The “deny” message indicates that thesubscriber was found not to have rights to the resource (i.e., activeaccount but not active service). Alternatively, another type of messagemay be generated, such as one that instructs the subscriber how toupgrade to be able to obtain the content, or provide a one-time paymentto access the content, etc.

If the service details match the requirements for the requested content,a “permit” message is transmitted to the service provider 202 at step318. For example, if the service details indicate that the subscriber iscurrently purchasing a premium level of service, and the requestedcontent is within the premium package, the subscriber will be permittedaccess to the content. The “permit” message indicates that thesubscriber was found to have rights to the resource (i.e., activeaccount and active service).

In another variant, a rights “profile” or other data structure may besent along with (e.g., as part of) or pursuant to the “permit” message,so as to inform the service provider of any access or use restrictions(e.g., limited number of views, allowable viewing window, restriction ontrick mode or start over functions, limitations on copying/distribution,etc.). These rights/restrictions can be used by the service provider toconfigure the requested content for delivery, such as by embedding DRMdata or watermarking in the content before delivery, encrypting it, etc.

Lastly, at step 320, the service provider 202 may proceed according tothe authorization response. For example, if service is denied, theservice provider 202 provides a pre-defined message to the subscriberindicating the reason and/or instructions or a link for online help toaid in resolving the denial. If service is permitted, the protectedcontent may be delivered to the subscriber (consistent with any userestrictions or policies).

FIG. 4 illustrates an exemplary communication flow (ladder diagram) forproviding content delivery across one or more content delivery networksin the instance account linking is not used, according to one embodimentof the invention. As illustrated, the CPE 106 (or PMD 107 or otherclient device) requests a target resource from the service provider 202(step 401). The request may, for example, be as follows:

http://sp.example.com/myresource

At this point, the service provider 202 performs a security check onbehalf of the target resource. If a valid security context at theservice provider already exists, the requested resource may be provided.However, if a valid security context is not yet established, the serviceprovider 202 responds to the CPE 106 request (402). In one embodiment,the response comprises an XHTML form. For example, the following may beprovided:

<form method=“post” action=“https://idp.example.org/SAML2/SSO/POST” ...><input type=“hidden” name=“SAMLRequest” value=“request” /> <inputtype=“hidden” name=“RelayState” value=“token” /> ... <inputtype=“submit” value=“Submit” /> </form> © Copyright 2010 Time WarnerCable, Inc. All rights reserved.In one embodiment, the RelayState token is an opaque (e.g., obfuscated)reference to state information maintained at the service provider 202.In a further embodiment, the value of the SAMLRequest parameter is abase 64 encoding of the following <sampl:AuthnRequest> element:

<samlp:AuthnRequest xmlns:samlp=“urn:oasis:names:tc:SAML:2.0:protocol”xmlns:saml=“urn:oasis:names:tc:SAML:2.0:assertion” ID=“identifier_1”Version=“2.0” IssueInstant=“2004-12-05T09:21:59Z”AssertionConsumerServiceIndex=“0”><saml:Issuer>https://sp.example.com/SAML2</saml:Issuer><samlp:NameIDPolicy AllowCreate=“true”Format=“urn:oasis:names:tc:SAML:2.0:nameid-format:transient”/><samlp:RequestedAuthnContext comparison=“exact”><saml:AuthnContextDeclRef>secure/SPfederatedlogin/user/password/uri</saml:AuthnContextDeclRef> </samlp:RequestedAuthnContext></samlp:AuthnRequest> © Copyright 2010 Time Warner Cable, Inc. Allrights reserved.Before the <samlp:AuthnRequest> element is URL-encoded and inserted intothe XHTML form, it may first be deflated and base 64-encoded (in thatorder).

When the CPE 106 receives the response, it requests to sign on to thenetwork of the identity provider 210 (i.e., the MSO network) at step403. In one embodiment, the sign on comprises a so-called “singlesign-on (SSO)” service, wherein the subscribers need only to sign or login once in order to obtain access to protected content. The subscriber'ssingle sign on may be restricted to a prescribed period of time (e.g.,24 hours, etc.). For example, the user may issue a POST request to theSSO service at the identity provider 210 as follows:

POST /SAML2/SSO/POST HTTP/1.1 Host: ids.rr.com Content-Type:application/x-www-form-urlencoded Content-Length:nnnSAMLRequest=request&RelayState=token © Copyright 2010 Time Warner Cable,Inc. All rights reserved.In one embodiment, the values of the SAMLRequest and RelayStateparameters are taken from the XHTML form (discussed above). The identityprovider 210 processes the <samlp:AuthnRequest> element (by URLdecoding,base64-decoding and inflating the request, in that order) and performs asecurity check. If the user does not have a valid security context, theidentity provider identifies the user (discussed elsewhere herein).

Information is transmitted between the CPE 106 and the identity provider210 to validly identify and authenticate the user. A separate step forauthorizing the user may also be utilized. The identity providervalidates the request and responds with a document containing an XHTMLform which may, in one embodiment, be similar to the following:

<form method=“POST” enctype=“application/x-www-form-urlencoded”action=“https://sp.example.com/nidp/saml2/spassertion_consumer”> ...><input type=“hidden” name=“SAMLResponse” value=“response” /> <inputtype=“hidden” name=“RelayState” value=“token” /> ... <inputtype=“submit” value=“Submit” /> </form> © Copyright 2010 Time WarnerCable, Inc. All rights reserved.In one embodiment, the value of the RelayState parameter is the same asnoted above, and the value of the SAMLResponse parameter is the base64encoding of the following <samlp:Response> element, and within theResponse is the <saml:AttributeStatement> containing the value of thecustomer GUID, as follows:

<samlp:Response xmlns:samlp=“urn:oasis:names:tc:SAML:2.0:protocol”xmlns:saml=“urn:oasis:names:tc:SAML:2.0:assertion”Destination=“https://sp.example.com/nidp/saml2/spassertion_consumer”ID=“idfghgcHuJ.2GxV6FpTwSUmyLcB38”InResponseTo=“idBYATWWoPEdJEHL6OQxVNquwV6jU” IssueInstant=“2009-01-22T13:51:46Z”Version=“2.0”><saml:Issuer>https://twcidp.eng.rr.com/nidp/saml2/metadata</saml:Issuer><samlp:Status><samlp:StatusCodeValue=“urn:oasis:names:tc:SAML:2.0:status:Success”/></samlp:Status><saml:Assertion ID=“iduQtIUg3EXARC7IKMrjgvF4-rMiE” IssueInstant=“2009-01-22T13:51:47Z”Version=“2.0”><saml:Issuer>https://twcidp.eng.rr.com/nidp/saml2/metadata</saml:Issuer><ds:Signaturexmlns:ds=“http://www.w3.org/2000/09/xmldsig#”> ... ...<saml:AuthnStatement AuthnInstant=“2009-01-22T13:51:47Z”SessionIndex=“10F09FE88CABF6C223222A22E3F75F59”SessionNotOnOrAfter=“2009-01-22T14:06:47Z”><saml:AuthnContext><saml:AuthnContextDeclRef>secure/federatedlogin/user/password/uri</saml:AuthnContextDeclRef></saml:AuthnContext ></saml:AuthnStatement<saml:AttributeStatement><saml:Attributexmlns:xsd=“http://www.w3.org/2001/XMLSchema”xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”Name=“/op:OP/op:CustomizableStrings/op:CustomizableString1”NameFormat=“urn:oasis:names:tc:SAML:2.0:attrnameformat:basic”><saml:AttributeValue type=“xs:string”>5D8269B8-7DD5-6017- 0AA6-4AE5F9780F9E</saml:AttributeValue></saml:Attribute></saml:AttributeState© Copyright 2010 Time Warner Cable, Inc. All rights reserved.

Next, the identity provider 210 redirects the CPE 106 to the assertionconsumer service (step 404). The assertion consumer service is in theexemplary embodiment an application process which validates SAMLresponses. The identity provider sends a document to the serviceprovider that indicates whether the CPE is or is not authenticated,along with other information about the CPE. The assertion consumerservice is a sub-process of the service provider which receivesdocuments (assertions), validates the digital signatures therein,decrypting, and consuming data contained in the document. The CPE maythen be passed on to the service provider application. The assertionconsumer service responds to the identity service provider from theservice provider. The CPE 106 may then request assertions from theservice provider 202 (step 405). For example, a user agent running onthe CPE 106 (or PMD 107 or client) may issue a POST request to theassertion consumer service at the service provider 202 as follows:

POST /SAML2/SSO HTTP/1.1 Host: sp.example.com Content-Type:application/x-www-form-urlencoded Content-Length:nnnSAMLResponse=response&RelayState=token © Copyright 2010 Time WarnerCable, Inc. All rights reserved.The values of the SAMLResponse and RelayState parameters in the aboveexample may be taken from the XHTML form discussed above.

The assertion consumer service processes the response, creates asecurity context at the service provider 202, and redirects the CPE 106to the target resource at step 406. The CPE 106 then requests the targetresource at the service provider 202 (again) at step 407. In oneembodiment, the request is as follows:

https://sp.example.com/myresource

Since a security context exists, the service provider 202 returns therequested resource to the CPE 106 (step 408).

Authentication With Linked Accounts—

In one embodiment, a single subscriber may be authenticated only once(e.g., the aforementioned “single sign-on SSO”), the process creating alink between the MSO 201 information for the subscriber and the serviceprovider 202 information for the same subscriber (i.e., federating theaccounts). According to this embodiment, the subscriber will not have tobe authenticated each time they attempt to view content, but rather theyare authenticated only once. The model may utilize, for example, SAML2.0 for the authentication.

When a customer attempts to access secure content from the external webapplication 204, the service provider 202 makes a request to theidentity provider 210 to determine whether the user has anauthentication session. If needed the service provider 202 requireslogin and check for an association to an MSO 201, and may further checkthe entitlement levels (such as according to the methods discussed inco-owned, co-pending U.S. patent application Ser. No. 12/536,724entitled “SYSTEM AND METHOD FOR MANAGING ENTITLEMENTS TO DATA OVER ANETWORK”, previously incorporated herein. If no association is present,then the service provider 202 requests that the user “links” the user'sservice provider 202 identity with the user's MSO 201 identity. Theresponse from the MSO identity provider 210 contains the customer's(subscriber's) identification (GUID) and a pseudonym for linking theidentities. The service provider 202 stores the pseudonym along with theGUID for this customer in a persistent profile maintained thereon,rather than in a cookie on the subscriber's browser. The serviceprovider 202 then makes a request to the entitlement server 208 toobtain the entitlements for the subscriber using the GUID.

To accomplish the aforementioned account federation, the serviceprovider 202 must employ at least a basic mechanism for identitymanagement (such as e.g., an IDMS). An exemplary method for the deliveryof protected content to a user via a service provider 202 which utilizesfederation is illustrated in FIG. 5.

As shown, per step 502, the customer (via his/her CPE 106 or PMD 107)requests secure resources from the external web application 204. In oneembodiment, the customer must first log into the service provider 202 inorder to request access to the protected content (not shown). The typeof login (e.g., password and user ID combination, challenge question,user-specific graphic or icon, etc.), the information required at login,and the creation of a login identity for the service provider 202 areeach controlled by the service provider 202 itself. For example, theservice provider 202 may require the subscriber to identify him/herselfby e.g., providing an email address and password combination, whereasthe MSO login (information) may be unique and completely unrelated.

At step 504, the service provider 202 responds with an XHTML form thatPOSTs to the identity provider 210. In one embodiment, the messagecontains the following fields:

SAMLRequest containing a NameIDPolicy type of persistent

RequestedAuthnContext for the URI used to identify this service provider

RelayState (optional)

-   -   ® Copyright 2010 Time Warner Cable, Inc. All rights reserved.

In one embodiment the service provider 202 and identity provider 210, inthe deployment of the SAML 2.0 Web Browser SSO profile both utilize theHTTP POST binding. An exemplary identity provider 210 POST URL may be asfollows:

IDP POST URL: https://ids.rr.com/nidp/saml2/sso

If it is determined that a session already exists (not shown), thecontent may be provided to the user. The session would already exist, inone embodiment, if the subscriber has already logged onto the MSO loginpage, and/or if the subscriber GUID has already been stored at theservice provider 202 (and was provided with the request). In thesesituations, as discussed elsewhere herein, the MSO will automatically bemade aware of the user's credentials and that the user is authorized toreceive the content.

If, at step 506, the identity provider 210 determines that no securitycontext is in scope (i.e., no session has been established), the user isrouted to a login page associated with the MSO 201 (step 508). At thelogin page, the user enters his/her credentials and their validity isdetermined (step 510). If the credentials entered are not valid, anerror message will be displayed to the user (step 512). Alternatively,if the user as not yet established login credentials with the MSO 201,the user may be provided with an opportunity to do so (e.g., to generatea digital signature) as discussed in previously incorporated U.S. patentapplication Ser. No. 12/______ entitled “APPARATUS AND METHODS FORCONTENT DELIVERY AND MESSAGE EXCHANGE ACROSS MULTIPLE CONTENT DELIVERYNETWORKS”.

Although separate logins are required under this embodiment for theservice provider 202 and the MSO 201, it will be appreciated that theuser may use the same or similar information to log into both sites. Forexample, both the service provider 202 and the MSO 201 may permit theuser to use an email address as a username. Accordingly, a singlesubscriber may use the same username (email address) to log into bothsites.

Upon verification of the credentials (step 510), the identity provider210 returns a response. In one embodiment, the identity providerresponse comprises an XHTML form sent to the browser containing:

SAMLResponse containing a pseudonym and GUID

RelayState (if provided in the initial request discussed above)

-   -   Copyright 2010 Time Warner Cable, Inc. All rights reserved.

Next, the browser sends the request to an assertion consumer service atthe service provider 202 (as discussed above), the service provider 202requests user credentials (if necessary) and stores the GUID andpseudonym of the linked account (step 516). A renewed request is thensent to original target resource. An authorization (and/or entitlement)request is then made by the service provider 202 (step 518), and aresponse is received (step 520).

Lastly, at step 522, the resource is provided to the user.

FIG. 6 illustrates an exemplary communication flow (ladder diagram) forproviding content delivery across one or more content delivery networksin the instance account linking is used. As illustrated, the messageflow begins at step 601 with a request for a secured resource at theservice provider 202. The CPE 106, PMD 107 or other client device (viae.g., an HTTP user agent) requests a target resource at the serviceprovider 201. In one embodiment, the request is as follows:

https://sp.example.com/myresource

The service provider 201 then performs a security check on behalf of thetarget resource. If a valid security context at the service provideralready exists, the requested resource may be provided. However, if avalid security context is not yet established, the service provider 201responds with a document containing an XHTML form (step 602):

<form method=“post” action=“https://idp.example.org/SAML2/SSO/POST” ...><input type=“hidden” name=“SAMLRequest” value=“request” /> <inputtype=“hidden” name=“Relay State” value=“token” /> ... <inputtype=“submit” value=“Submit” /> </form> © Copyright 2010 Time WarnerCable, Inc. All rights reserved.In the above XHTML form, the RelayState token is an opaque reference tostate information maintained at the service provider 202, and the valueof the SAMLRequest parameter is the base64 encoding of the following<samlp:AuthnRequest> element:

<samlp:AuthnRequest xmlns:samlp=“urn:oasis:names:tc:SAML:2.0:protocol”xmlns:saml=“urn:oasis:names:tc:SAML:2.0:assertion” ID=“identifier_1”Version=“2.0” IssueInstant=“2004-12-05T09:21:59Z”AssertionConsumerServiceIndex=“0”><saml:Issuer>https://sp.example.com/SAML2</saml:Issuer><samlp:NameIDPolicy AllowCreate=“true”Format=“urn:oasis:names:tc:SAML:2.0:nameid-format:persistent”/><samlp:RequestedAuthnContext comparison=“exact”><saml:AuthnContextDeclRef>secure/SPfederatedlogin/user/password/uri</saml:AuthnContextDeclRef> </samlp:RequestedAuthnContext></samlp:AuthnRequest> © Copyright 2010 Time Warner Cable, Inc. Allrights reserved.In one embodiment, before the <samlp.AuthnRequest> element isURL-encoded and inserted into the XHTML form (above), it is firstdeflated and base64-encoded (in that order).

Next, the CPE 106 (or PMD 107) issues a POST request to the identityprovider 210 (step 603). In one embodiment the POST request is asfollows:

POST /SAML2/SSO/POST HTTP/1.1 Host: ids.rr.com Content-Type:application/x-www-form-urlencoded Content-Length:nnnSAMLRequest=request&RelayState=token © Copyright 2010 Time Warner Cable,Inc. All rights reserved.In the above embodiment, the values of the SAMLRequest and RelayStateparameters may be taken from the XHTML form discussed above. Theidentity provider 210 processes the <samlp:AuthnRequest> element (byURLdecoding, base64-decoding and inflating the request, in that order)and performs a security check. If the user does not have a validsecurity context, the identity provider identifies the user (asdiscussed elsewhere herein).

Next, the identity provider 210 validates the request and responds witha document containing an XHTML form, such as that presented below:

<form method=“POST” enctype=“application/x-www-form-urlencoded”action=“https://sp.example.com/nidp/saml2/spassertion_consumer”> ...><input type=“hidden” name=“SAMLResponse” value=“response” /> <input type=“hidden” name=“RelayState” value=“token” /> ... <input type=“submit”value=“Submit” /> </form> © Copyright 2010 Time Warner Cable, Inc. Allrights reserved.In the above example, the value of the RelayState parameter is the sameas that previously discussed, and the value of the SAMLResponseparameter is the base64 encoding of the following <samlp:Response>element, and within the Response is the <saml:AttributeStatement>containing the value of the customer GUID:

<samlp:Response xmlns:samlp=“urn:oasis:names:tc:SAML:2.0:protocol”xmlns:saml=“urn:oasis:names:tc:SAML:2.0:assertion”Destination=“https://sp.example.com/nidp/saml2/spassertion_consumer”ID=“idfghgcHuJ.2GxV6FpTwSUmyLcB38”InResponseTo=“idBYATWWoPEdJEHL6OQxVNquwV6jU” IssueInstant=“2009-01-22T13:51:46Z”Version=“2.0”><saml:Issuer>https://twcidp.eng.rr.com/nidp/saml2/metadata</saml:Issuer><samlp:Status><samlp:StatusCodeValue=“urn:oasis:names:tc:SAML:2.0:status:Success”/></samlp:Status><saml :Assertion ID=“iduQtIUg3EXARC7IKMrjgvF4-rMiE”IssueInstant=“2009-01- 22T13:51:47Z”Version=“2.0”><saml:Issuer>https://twcidp.eng.rr.com/nidp/saml2/metadata</saml:Issuer><ds:Signaturexmlns:ds=“http://www.w3.org/2000/09/xmldsig#”> ... ...<saml:AuthnStatement AuthnInstant=“2009-01-22T13:51:47Z”SessionIndex=“10F09FE88CABF6C223222A22E3F75F59”SessionNotOnOrAfter=“2009-01-22T14:06:47Z”><saml:AuthnContext><saml:AuthnContextDeclRef>secure/federatedlogin/user/password/uri</saml:AuthnContextDeclRef></saml:AuthnContext ></saml:AuthnStatement><saml:AttributeStatement><saml:Attributexmlns:xsd=“http://www.w3.org/2001/XMLSchema”xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”Name=“/op:OP/op:CustomizableStrings/op:CustomizableString1”NameFormat=“urn:oasis:names:tc:SAML:2.0:attrnameformat:basic”><saml:AttributeValue type=“xs:string”>5D8269B8-7DD5-6017- 0AA6-4AE5F9780F9E</saml:AttributeValue></saml:Attribute></saml:AttributeState© Copyright 2010 Time Warner Cable, Inc. All rights reserved.

Next, the identity provider 210 redirects the CPE 106 to the assertionconsumer service (step 604). The client (e.g., CPE 106) may issue a POSTrequest to the assertion consumer service at the service provider 202(step 605). In one example, the request is as follows:

POST /SAML2/SSO HTTP/1.1 Host: sp.example.com Content-Type:application/x-www-form-urlencoded Content-Length:nnnSAMLResponse=response&RelayState=token © Copyright 2010 Time WarnerCable, Inc. All rights reserved.In the above embodiment, the values of the SAMLResponse and RelayStateparameters may be taken from the XHTML form previously discussed.

The assertion consumer service processes the response, creates asecurity context at the service provider and redirects the CPE 106 (orPMD 107) to the target resource (step 606). The CPE 106 then requeststhe target resource at the service provider (again) at step 607. In oneembodiment, the request appears as follows:

https://sp.example.com/myresource

As noted above, in one embodiment the entitlements of the requestinguser may be determined, such as is described in previously referencedco-owned, co-pending U.S. patent application Ser. No. 12/536,724 filedon Aug. 6, 2009 and entitled “SYSTEM AND METHOD FOR MANAGINGENTITLEMENTS TO DATA OVER A NETWORK”.

Next, since a security context exists, the service provider 202 returnsthe resource to the CPE 106 (step 608).

Account Decoupling (De-Federation)—

As noted above, the service provider 202 may in certain embodimentsutilize a separate IDMS, and may link a subscriber account containedtherein to an MSO 201 subscriber account for the same subscriber orentity. Once an account has been linked, there may be conditions(whether based on policy or by the election of the user) which requirethat the link between the accounts be terminated. For example, if thesubscriber is no longer a customer of a first MSO, and instead now is acustomer of a second MSO, unlinking or de-federation will be necessary.In one embodiment, the termination is executed by the service provider202 sending a termination request to the identity provider 210 (e.g.,MSO) over a Simple Object Access Protocol (SOAP) back channel, or viaanother available communications channel.

FIG. 7 illustrates one embodiment of an exemplary method which maygenerally be used for decoupling or unlinking a subscriber accountaccording to the present invention.

As shown, per step 702 a request to de-federate the account is receivedfrom the subscriber (or other instigator) at the service provider 202.In response to receiving the subscriber request, the service provider202 develops a request to be sent to the MSO 201 (step 704). In oneembodiment, the service provider 202 utilizes the Name IdentifierManagement Protocol (as discussed in the previously referenced SAML 2.0specification) to generate and send the request to the identity provider210 or other designated entity, for example, an <ManageIDNameRequest>containing the subscriber's pseudonym may be sent.

The identity provider 210 (and/or other MSO 201 entities) processes therequest at step 706. The identity provider 210 then returns a “success”or “failure” message comprising the <ManageIDNameResponse> with theappropriate status code therein, at step 708. For example, if therequest is processed successfully, a verification code is returned tothe service provider 202 comprising a <ManageIDNameResponse> with a codeverifying the success of the unlinking. If the de-federation issuccessful, any future attempts by the subscriber to view protectedcontent will be denied. If the request is not processed successfully, afailure message comprising a <ManageIDNameResponse> with a codeindicating the failure of the unlinking is returned. The serviceprovider 202 may initiate another request if the response provided bythe MSO 201 indicates failure to unlink the accounts.

Referring now to FIG. 8, an exemplary communication flow between theservice provider 202 and the identity provider 210 is illustrated. Asshown, the service provider 202 sends to the identity provider 210 a<ManageIDNameRequest> defining that the persistent identifier(previously established) must no longer be used at step 801. In oneembodiment, the request is carried in a SOAP message which istransported using HTTP, as defined by the SAML SOAP binding. The requestis also digitally signed by the service provider. An exemplary requestis illustrated below:

<SOAP-ENV:Envelope xmlns:SOAP-ENV=“http://schemas.xmlsoap.org/soap/envelope/”> <SOAP-ENV:Body><saml:Issuer> https://sp.example.com/nidp/saml2/metadata </saml:Issuer><ds:Signature xmlns:ds=“http://www.w3.org/2000/09/xmldsig#”><ds:SignedInfo> <ds:CanonicalizationMethodAlgorithm=“http://www.w3.org/2001/10/xml-exc-c14n#”/><ds:SignatureMethodAlgorithm=“http://www.w3.org/2000/09/xmldsig#rsa-sha1”/> <ds:ReferenceURI=“#idioAMRYUXbAhxlAdA0nCVN9jlt84”> <ds:Transforms> <ds:TransformAlgorithm=“http://www.w3.org/2000/09/xmldsig#enveloped-signature”/><ds:Transform Algorithm=“http://www.w3.org/2001/10/xml-exc-c14n#”/></ds:Transforms> <ds:DigestMethodAlgorithm=“http://www.w3.org/2000/09/xmldsig#sha1”/> </ds:DigestValue></ds:Reference> </ds:SignedInfo> <ds:SignatureValue> ...REMOVED FORBREVITY... </ds:SignatureValue> <ds:X509Certificate> ...REMOVED FORBREVITY... </ds:X509Certificate> </ds:X509Data> </ds:KeyInfo></ds:Signature> <saml:NameIDFormat=“urn:oasis:names:tc:SAML:2.0:nameidformat: persistent”NameQualifier=“https://ids.eng.rr.com/nidp/sa ml2/metadata”SPNameQualifier=“https://sp.example.com/nidp/saml2/metadata”>k1H7+36rgRfM2az7hNSh+4PRo/OL36X78div7A== </saml:NameID><samlp:Terminate/> </samlp:ManageNameIDRequest> </SOAP-ENV:Body></SOAP-ENV:Envelope> © Copyright 2010 Time Warner Cable, Inc. All rightsreserved.

Next, at step 802, a response is received from the identity provider210. In one embodiment, the response is carried within a SOAP over HTTPmessage and is digitally signed. An exemplary response is illustratedbelow:

<samlp:ManageNameIDResponse ID=“idxRslo7vdwTn6YnlTjB9pUnjsBkg”InResponseTo=“idioAMRYUXbAhxlAdAOnCVN9jlt84” IssueInstant=“2009-01-26T16:42:50Z” Version=“2.0”xmlns:saml=“urn:oasis:names:tc:SAML:2.0:assertion”xmlns:samlp=“urn:oasis:names:tc:SAML:2.0:protocol”> <saml:Issuer>https://ids.eng.rr.com/nidp/saml2/metadata </saml:Issuer> <ds:Signaturexmlns:ds=“http://www.w3.org/2000/09/xmldsig#”> <ds:SignedInfo><ds:CanonicalizationMethodAlgorithm=“http://www.w3.org/2001/10/xml-exc-c14n#”/><ds:SignatureMethodAlgorithm=“http://www.w3.org/2000/09/xmldsig#rsa-sha1”/> <ds:ReferenceURI=“#idxRslo7vdwTn6YnlTjB9pUnjsBkg”> <ds:Transforms> <ds:TransformAIgorithm=“http://www.w3.org/2000/09/xmldsig#enveloped-signature”/><ds:TransformAlgorithm=“http://www.w3.org/2001/10/xm lexc-c14n#”/></ds:Transforms> <ds:DigestMethodAlgorithm=“http://www.w3.org/2000/09/xmldsig#sha1”/> <ds:DigestValue>EPq52hQmKDDnijT5lhO0gdVR7LA= </ds:DigestValue> </ds:Reference></ds:SignedInfo> <ds:SignatureValue> ...REMOVED FOR BREVITY...</ds:SignatureValue> <ds:KeyInfo> <ds:X509Data> <ds:X509Certificate>...REMOVED FOR BREVITY... </ds:X509Certificate> </ds:X509Data></ds:KeyInfo> </ds:Signature> <samlp:Status> <samlp:StatusCodeValue=“urn:oasis:names:tc:SAML:2.0:status:Success”/> </samlp:Status></samlp:ManageNameIDResponse> © Copyright 2010 Time Warner Cable, Inc.All rights reserved.

Usage Data Collection and Billing Mechanisms—

In yet another embodiment, various data collection entities may beutilized at e.g., the MSO 201 and/or content/service provider 202 whichare configured to collect data regarding content usage at the CPE, PMDor other client device. For example, the collection entities may beconfigured to store data records relating to the content requested byindividual ones of the devices. In this manner, the collection entitiesmay develop statistics relating to the frequency of requests fromindividual users, the types of content requested (such as genre,premium, pay-per-view, etc.), etc. The collection entities may also beconfigured to receive upstream communications from the devices regardinginteractions of the user with the requested content. For example, thecollection entities may create data records relating to the trick modeoperations employed by the users, including the periods during which thetrick modes are operated (such as e.g., during advertisements, etc.).

The usage data may, in one embodiment, be further used for billingpurposes. For example, in one billing paradigm a user may be charged apremium for utilization of the herein described services based on thenumber of content hours watched or received, and/or the types of contentbeing requested. In one embodiment, while certain content may beprovided at no additional costs to a subscriber in conjunction with thesubscriber's subscription plan with the MSO, other content (such aspremium content, pay-per-view content, on-demand content, contentoutside of the subscriber's subscription plan, etc.) may be provided tothe subscriber for additional cost. The aforementioned data collectionmechanisms may then be utilized to generate billing records for thesubscriber's content requests. In another embodiment, the number ofrequests and/or the actual time (in hours, minutes, etc.) spentaccessing (or watching) the requesting content is recorded and used forgenerating billing records. The generated billing records aretransmitted to e.g. a billing system which generates bills to thecustomer for accessing content outside of or in addition to, his/hersubscription plan.

It is further appreciated that the foregoing methods for providingcontent to a requesting subscriber (e.g., the methods of FIGS. 3 and 5)may also include providing one or more confirmation screens to thesubscriber indicating a price associated with the requested content, andrequiring the subscriber's affirmative permission to charge that priceto the subscriber's account with the MSO. In one embodiment, thepermission may be in the form of a simple button press, alternatively,the subscriber may be required to enter an access code or otherindicator of the subscriber's intent to have the associated costs billedto their account.

Security and Other Content Configuration—

In yet another embodiment, digital rights management (DRM) or otherforms of rights/content protection (e.g., use of encryption keys,cryptographic residue or hashing for integrity protection, etc.) may beused consistent with delivery of the content. For instance, in oneimplementation, the necessary cryptographic data (e.g., keys) arepre-positioned at the service provider 202 to enable the serviceprovider 202 to enforce security rights on content authorized fordelivery. In this manner, the MSO 201 can maintain control over thecontent although it has left the boundaries of the MSO network. Theservice provider 202 may apply DRM or other rights management mechanismsto the requested content prior to delivery to the subscriber accordingto MSO policy. The DRM or other rights management mechanism may begeneric, or alternatively specific to the requesting subscriber. Forinstance, each subscriber is assigned an encryption key (e.g.,public/private key pair, or asymmetric key) that is always applied tocontent provided thereto, the encryption key(s) being linked to thesubscriber such as by GUID. For example, a user may be assigned a keypair for its content requests; the content source then encrypts anyrequested for content from that user with the user's specific key pair.

In addition, integrity protection (such as via a one-way hashingalgorithm of the type well known in the art) may optionally be appliedto the content during transmission so as to assure that it has not beentampered with or otherwise compromised.

In another embodiment, the service provider 202 may furtherpre-configure the requested content based on one or more configurationparameters associated with the requesting device. For example, the MSO201 may provide information to the service provider 202 (or the clientdevice may provide this information directly to the content/serviceprovider) indicating the capabilities of each of the devices associatedwith a particular subscriber. The information may e.g., identify thedevice by MAC address or other unique identifier, and identify the userby GUID. The service provider 202 stores this information and, when arequest is received from a particular device, the service provider 202automatically pre-configures the content for delivery thereto based onwhat is known about the particular requesting device. For example, theservice provider 202 may be informed of e.g., the available codecs, DRM,display capabilities, etc. that are available at a user device. Theservice provider 202 may configure the content according to these knowncapabilities, such as by changing the display resolution, bitrate,encoding scheme, QoS policies applied, encapsulation protocol, etc.

The delivery of capabilities information (e.g., by the MSO 201) prior toany content requests enables more efficient delivery of content withoutthe user experiencing incompatibilities or non-optimized viewing of therequested content. Moreover, where the MSO pre-positions theconfiguration information, negotiation between the service provider 202and the device(s) individually (and/or with the MSO 201 at each contentrequest) are advantageously obviated.

Single Log Out (SLO)—

The single log out (SLO) process is utilized where a non-linked customerhas established a session at the service provider 202, and the customerelects to log out of the service provider 202 site. In order toaccomplish the log out, the service provider 202 sends a log out requestto the identity provider 210 in order to ensure that the identityprovider 210 destroys the authenticated session on its side (i.e., atthe MSO 201) thereby ensuring maximum security for the customer.

In the exemplary embodiment, the service provider 202 is responsible fordisplaying the success of the log out request after the browser isreturned to the service provider 202 following a successful SLO.

FIG. 9 illustrates an exemplary embodiment of the method for SLO. Perstep 902, the customer elects to log out of the service provider's site.The request is forwarded to the MSO at step 904. In other words, theservice provider 202 responds with an XHTML form that POSTs to theidentity provider 210 (such as at a SLO service maintained thereon). Inone implementation, the XHTML form comprises a SAMLRequest with thefollowing fields:

LogoutRequest

Transient NameID pseudonym

Session Index—optional

-   -   © Copyright 2010 Time Warner Cable, Inc. All rights reserved.

Next, at step 906, the identity provider 210 (and/or other MSO 201entities) processes the request. A response to the request is returnedat step 908. In one embodiment the response to the request comprises anXHTML form to the browser redirecting the browser to the serviceprovider SLO return URL. The XHTML form may, for example, contain aSAMLResponse with the following field(s):

LogoutResponse

Status

Per step 910, the service provider 202 displays a message that thesession has been successfully logged out.

Referring now to FIG. 10, an exemplary message flow between the serviceprovider 202, CPE 106 (and/or PMD 107) and identity provider 210 isillustrated. As shown, the customer (via a user agent running on his/herCPE 106, PMD 107, or other client) requests the logout link in theservice provider 202 site to terminate their session (step 1001). Atstep 1002, the service provider 202 responds with a document which inone embodiment contains an XHTML form, such as:

<form method=“POST” enctype=“application/x-www-form-urlencoded”action=“https://twcidp.eng.rr.com/nidp/saml2/slo”> <input type=“hidden”name=“SAMLRequest” value=“PHNhbWxwOkx.../> </form> © Copyright 2010 TimeWarner Cable, Inc. All rights reserved.

In the above embodiment, the value of the SAMLRequest parameter may bethe base64 encoding of the following <samlp:LogoutRequest> element:

<samlp:LogoutRequest xmlns:samlp=“urn:oasis:names:tc:SAML:2.0:protocol”xmlns:saml=“urn:oasis:names:tc:SAML:2.0:assertion”Destination=“https://ids.rr.com/nidp/saml2/slo”ID=“idIqkPGaaUhuxzpwd8EbMoNs4WnIs” IssueInstant=“2009-03-23T17:07:21Z”Version=“2.0”><saml:Issuer>https://sp.example.com/saml2/metadata</saml:Issuer><ds:Signature xmlns:ds=“http://www.w3.org/2000/09/xmldsig#”> <ds:SignedInfo><ds:CanonicalizationMethodAlgorithm=“http://www.w3.org/2001/10/xml-exc-c14n#”/><ds:SignatureMethodAlgorithm=“http://www.w3.org/2000/09/xmldsig#rsa-sha1”/> <ds:ReferenceURI=“#idIqkPGaaUhuxzpwd8EbMoNs4WnIs”> <ds:Transforms> <ds:TransformAlgorithm=“http://www.w3.org/2000/09/xmldsig#enveloped-signature”/><ds:Transform Algorithm=“http://www.w3.org/2001/10/xml-exc-c14n#”/></ds:Transforms> <ds:DigestMethodAlgorithm=“http://www.w3.org/2000/09/xmldsig#sha1”/><ds:DigestValue>pAmFDNUTl7TAzVcNRFBTZ8SRng8=</ds:DigestValue></ds:Reference> </ds:SignedInfo> <ds:SignatureValue> ZUE29+Ppi+/==</ds:SignatureValue> <ds:KeyInfo> <ds:X509Data> <ds:X509Certificate>MIIFNzCCBB+== </ds:X509Certificate> </ds:X509Data> </ds:KeyInfo></ds:Signature><saml:NameIDFormat=“urn:oasis:names:tc:SAML:2.0:nameidformat: transient”NameQualifier=“https://ids.rr.com/nidp/saml2/metadata”SPNameQualifier=“https://sp.example.com/saml2/metadata”>ktEBMsAYiJGslOG2yZznu8Gb6LXPleO9t57pqg==</saml:NameID></samlp:LogoutRequest> © Copyright 2010Time Warner Cable, Inc. All rights reserved.

Before the <samlp:LogoutRequest> element is URL-encoded and insertedinto the XHTML form, it is first deflated and base64-eneoded (in thatorder).

Next, the user agent (running on the CPE 106 and/or PMD 107) issues aPOST request to the identity provider 210 at step 1003. In oneembodiment, the request is structured as follows:

POST /nidp/saml2/slo HTTP/1.1 Host: ids.rr.com Content-Type:application/x-www-form-urlencoded Content-Length:nnnSAMLRequest=request&RelayState=token © Copyright 2010 Time Warner Cable,Inc. All rights reserved.In the above embodiment, the values of the SAMLRequest parameter may betaken from the XHTML form previously discussed. The SLO service (runningat the identity provider 210 and/or other MSO 201 entity) processes the<samlp:LogoutRequest> element (by URL-decoding, base64-decoding andinflating the request, in that order) and performs session terminateprocess.

Next, the SLO service validates the request and responds with a documentcontaining an XHTML form (step 1004). An exemplary XHTML form is asfollows:

<form method=“POST” enctype=“application/x-www-form-urlencoded”action=“https://sp.example.com/saml2/spslo_return”> <input type=“hidden”name=“SAMLResponse” value=“PHNhbWxwOkxvZ291dFJl.../> </form> © Copyright2010 Time Warner Cable, Inc. All rights reserved.In the above example, the value of the SAMLResponse parameter may be thebase64 encoding of the following <samlp:LogoutResponse> element, andwithin the LogoutReponse is the <samlp:StatusCode> stating the successor failure of the request:

<samlp:LogoutResponse xmlns:samlp=“urn:oasis:names:tc:SAML:2.0:protocol”xmlns:saml=“urn:oasis:names:tc:SAML:2.0:assertion”Destination=“https://sp.example.com/saml2/spslo_return”ID=“iduqo4LnN1QCiNZwQkXasCYg79k4”InResponseTo=“idIqkPGaaUhuxzpwd8EbMoNs4WnIs” IssueInstant=“2009-03-23T17:07:21Z”Version=“2.0”><saml:Issuer>https://ids.rr.com/nidp/saml2/metadata</saml:Issuer><ds:Signature xmlns:ds=“http://www.w3.org/2000/09/xmldsig#”><ds:SignedInfo> <ds:CanonicalizationMethodAlgorithm=“http://www.w3.org/2001/10/xml-exc-c14n#”/><ds:SignatureMethodAlgorithm=“http://www.w3.org/2000/09/xmldsig#rsa-sha1”/> <ds:ReferenceURI=“#iduqo4LnN1QCiNZ-wQkXasCYg79k4”> <ds:Transforms><ds:TransformAlgorithm=“http://www.w3.org/2000/09/xmldsig#enveloped-signature”/><ds:Transform Algorithm=“http://www.w3.org/2001/10/xml-exc-c14n#”/></ds:Transforms> <ds:DigestMethodAlgorithm=“http://www.w3.org/2000/09/xmldsig#sha1”/><ds:DigestValue>dwP26GAgmj3Ck92ZNs/7RYsw4ko=</ds:DigestValue></ds:Reference> </ds:SignedInfo> <ds:SignatureValue> B4B7q7m7RwcZ+==</ds:SignatureValue> <ds:KeyInfo> <ds:X509Data> <ds:X509Certificate>MIIFNzCCBB+== </ds:X509Certificate> </ds:X509Data> </ds:KeyInfo></ds:Signature><samlp:Status><samlp:StatusCodeValue=“urn:oasis:names:tc:SAML:2.0:status:Success”/></samlp:Status></samlp:LogoutResponse> © Copyright 2010 Time Warner Cable, Inc. All rightsreserved.Next, the SLO return URL is requested at the service provider 202 (step1005), and the service provider 202 displays the successful logoutrequest (step 1006).

Cancel Login—

If/when a subscriber is sent to the identity provider 210 login page toauthenticate (as discussed above), the subscriber can decide to cancelthe authentication transaction. Canceling the transaction may benecessary for any reason, and this facility generically allows a SAMLresponse to be sent back to the service provider 202 so the transactioncan be ended. For example, the login cancel may be triggered when thecustomer no longer wants their identity with the MSO 201 to be linked tothat of the service provider 202, or in the instance where the serviceprovider 202 has deleted the user's identity from its system.

FIG. 11 illustrates a method for the cancellation of a login accordingto one embodiment of the present invention. As illustrated per step1102, the “terminate” request is sent to the identity provider 210,and/or other entities of the MSO 201. In one implementation, theterminate request uses the aforementioned Name Identifier ManagementProtocol, specifically using the

<ManageNameIDRequest>.

At step 1104, the MSO 201 processes the request, and at step 1106returns a response. In one embodiment, the response comprises a<ManageIDNameResponse> containing a suitable status code response. Theresponse is for example carried within a SOAP over HTTP message and isdigitally signed. The response message is then displayed to the user(step 1108)

FIG. 12 illustrates the interaction between the service provider 202 andthe identity provider 210, as discussed above, for the cancellation of alogin. As shown, the service provider 202 sends to the identity provider210 a <ManageIDNameRequest> defining that the persistent identifier(previously established) must no longer be used (step 1201). The requestis carried in a SOAP message which is transported using HTTP, as definedby the SAML SOAP binding. The request may also be digitally signed bythe service provider 202. The following illustrates an exemplaryrequest:

<SOAP-ENV:Envelope xmlns:SOAP-ENV=“http://schemas.xmlsoap.org/soap/envelope/”> <SOAP-ENV:Body><saml:Issuer> https://sp.example.com/nidp/saml2/metadata </saml:Issuer><ds:Signature xmlns:ds=“http://www.w3.org/2000/09/xmldsig#”><ds:SignedInfo> <ds:CanonicalizationMethodAlgorithm=“http://www.w3.org/2001/10/xml-exc-c14n#”/><ds:SignatureMethodAlgorithm=“http://www.w3.org/2000/09/xmldsig#rsa-sha1”/> <ds:ReferenceURI=“#idioAMRYUXbAhxlAdA0nCVN9jlt84”> <ds:Transforms> <ds:TransformAlgorithm=“http://www.w3.org/2000/09/xmldsig#enveloped-signature”/><ds:Transform Algorithm=“http://www.w3.org/2001/10/xml-exc-c14n#”/></ds:Transforms> <ds:DigestMethodAlgorithm=“http://www.w3.org/2000/09/xmldsig#sha1”/> </ds:DigestValue></ds:Reference> </ds:SignedInfo> <ds:SignatureValue> ...REMOVED FORBREVITY... </ds:SignatureValue> <ds:X509Certificate> ...REMOVED FORBREVITY... </ds:X509Certificate> </ds:X509Data> </ds:KeyInfo></ds:Signature> <saml:NameIDFormat=“urn:oasis:names:tc:SAML:2.0:nameidformat: persistent”NameQualifier=“https://twcidp.eng.rr.com/nidp/sa ml2/metadata”SPNameQualifier=“https://sp.example.com/nidp/saml2/metadata”>k1H7+36rgRfM2az7hNSh+4PRo/OL36X78div7A== </saml:NameID><samlp:Terminate/> </samlp:ManageNameIDRequest> </SOAP-ENV:Body></SOAP-ENV:Envelope> © Copyright 2010 Time Warner Cable, Inc. All rightsreserved.

Lastly, at step 1202, a response is received from the identity provider210. As above, the response is carried within a SOAP over HTTP messageand is digitally signed in one embodiment.

Exemplary User Device—

Generally, the exemplary user devices (e.g., CPE 106 and/or PMD 107)useful with the present invention will include e.g., a network interface(including an interface for accessing the Internet via the designatedbearer medium; e.g., MSO network, non-managed network, etc.), aprocessor and associated storage, and optionally a plurality of back endinterfaces for communication with other devices. The user device canassume literally any discrete form factor, including those adapted forsettop/desktop, hand-held, or wall-mounted use, or alternatively may beintegrated in whole or part (e.g., on a common functional basis) withother devices if desired. Additionally, the user device may includeother elements and interfaces such as for example an interface for theHomePlug AN standard which transmits digital data over power lines, aPAN (e.g., 802.15), Bluetooth, or other short-range wireless interfacefor localized data communication, etc.

In one embodiment, the network interface receives content and/or datavia one or more RF tuners configured to receive content from an HFCnetwork 101. The RF tuner(s) may comprise traditional video RF tuner(s)adapted to receive video signals over, e.g., a QAM. For example, the RFtuner(s) may comprise one or more tuners, a demodulator, decryptionmodule, and demultiplexer of the type well known in the art, althoughother configurations may be used. A wideband tuner arrangement such asthat described in co-owned and co-pending U.S. patent application Ser.No. 11/013,671 entitled “METHOD AND APPARATUS FOR WIDEBAND DISTRIBUTIONOF CONTENT” filed Dec. 15, 2004 and incorporated herein by reference inits entirety, may also be utilized, such as where the content associatedwith one or more program streams is distributed across two or more QAMs.Additionally, the RF tuner(s) may incorporate functionality to modulate,encrypt/multiplex as required, and transmit digital information forreceipt by upstream entities such as the CMTS.

Alternatively, the network interface may comprise any other means forreceiving content from a network. For instance, the device may comprisea Wi-Fi or WiMAX enabled smartphone or laptop with connectivity to therelevant wireless service provider, which ultimately connects to theunmanaged network (e.g., Internet).

Digital data received via the network interface may include for exampleMPEG-2 or H.264 encoded programming data that is forwarded to atelevision or other device monitor via a video interface. Programmingdata may also be stored on the storage unit for later distribution byway of the video interface, or using a Wi-Fi interface, Ethernetinterface, FireWire (IEEE Std 1394), USB/USB2, or any number of othersuch options.

Programming and other types of data including pictures, video, music orMP3 files, software applications, metadata files, etc. may also bereceived by way of the various digital interfaces in the user device.These data may be stored locally (e.g., in the storage unit) or even ona device or network agent in communication with the user device, forlater use by a user as is discussed in co-owned co-pending U.S. patentapplication Ser. No. 11/378,129 entitled “METHODS AND APPARATUS FORCENTRALIZED CONTENT AND DATA DELIVERY”, previously incorporated herein.

During operation of the user device, a client application (located inthe storage unit) is run on the microprocessor. The client applicationfollows appropriate protocol for sending requests for content andreceiving requested content as well as for providing additionalinformation to the network to facilitate authentication and federation(discussed above) by providing information regarding the subscriber/userand/or device to the network entities discussed above. For example, theclient application may provide subscriber account information and/orlogin information upstream in order for the identity provider 210,service provider 202, and other entities to identify the subscriber andprovide content based on what is known (at the MSO 201 and/or serviceprovider 202) about the subscriber.

While the foregoing embodiments of the invention have been describedprimarily with respect to the network-side elements (i.e.,content/service provider 202, MSO 201, etc.), it will be appreciatedthat other implementations of the invention may utilize a speciallyadapted CPE 106 or client device (e.g., PMD 107) used by the subscriberin generating the request for protected content. For example, the CPE orclient software application or stack component may obtain and formatrequest messages or other messages (e.g., logins) for certain externalweb applications 204 according to a prescribed configuration. In onesuch implementation, a subscriber accesses a designated external webapplication 204, wherein the website 204 passes the subscriber itsprogrammer GUID or other identifying information. The client applicationthen uses this information to recognize the site as “MSO affiliated”,and thereby necessarily being compliant with the aforementionedprotocols discussed above. The client application then formats andrequests for protected content or other messages between the subscriberdevice and that website 204 according to the supported protocols, suchas by including MAC address, subscriber GUID, etc. In this fashion, thewebsite 204 is relieved of some of the burden of such formatting, andone or more subsequent messages between the two entities may be obviated(i.e., the website does not have to go back and ask the client devicefor each requisite piece of information it requires to process thesubscriber's request).

In another embodiment, the various restrictions (if any) to theprovision of content to a user at a display or rendering deviceassociated with the user device are determined by the device (e.g., CPE106, PMD 107, etc.) itself, as discussed in co-owned, co-pending U.S.patent application Ser. No. 12/716,131 filed on Mar. 2, 2010 andentitled “APPARATUS AND METHODS FOR RIGHTS-MANAGED CONTENT AND DATADELIVERY”, which is incorporated herein by reference in its entirety. Asdiscussed therein, a downloadable or transferable rights profile coupledwith a “smart” media player application are given. The rights profilecontains information regarding the specific rights of a device and/or asubscriber to access content. It is via the rights profile that thedevice (via the media player and its associated rights managementapplication) determines whether to provide content to a subscriber,and/or what restrictions or privileges to apply. Hence, in the presentcontext, the MSO might generate a rights profile and pass this profile(or information indicating which of a plurality of pre-positionedprofiles to apply) to the service provider 202 for transmission to thesmart media player on the client device.

In addition, the client application may be configured to collectinformation regarding the user's actions with respect to content, andpass this upstream (whether to the service provider 202 or the MSO 201).For example, the client application may record button presses, playbackevents, trick mode events, etc. and pass this information to MSO 201entities which may use the information to make various businessdecisions including e.g., secondary content insertion decisions.

Methods and apparatus for providing such secondary content insertion maybe of the type discussed in co-owned, co-pending U.S. patent applicationSer. No. 11/441,476 filed on May 24, 2006 and entitled “SECONDARYCONTENT INSERTION APPARATUS AND METHODS”, which is incorporated hereinby reference in its entirety, and may be utilized to provide dynamicsecondary content insertion (e.g., replacement of dated orgeographically inappropriate advertisements or promotions), and therebyallow the MSO 201 or other network operator to adjust the secondarycontent to make it more applicable to the remote user's context (e.g.,location, hardware/software environment, date/time, etc.). Additionally,the apparatus and methods discussed in co-owned, co-pending U.S. patentapplication Ser. No. 11/198,620 filed on Aug. 4, 2005 and entitled“METHOD AND APPARATUS FOR CONTEXT-SPECIFIC CONTENT DELIVERY”, which isincorporated herein by reference in its entirety, may be utilizedconsistent with the present invention. As discussed therein,contextually-related “secondary” content (e.g., advertising messages,useful informational links, etc.) may be provided in association withother primary content selected by the user.

Anonymity—

As noted above, certain data (including collected data, etc.) may beparticular to or identified with a particular subscriber, user, or userdevice. Accordingly, such data may, in addition to being obfuscated asdescribed above, also be anonymized by inter cilia, the use of acryptographic hash to protect the privacy of the identified subscriber,user, and/or device. In one embodiment, the techniques for providinganonymity utilizing a cryptographic hash described in U.S. patentapplication Ser. No. 11/186,452 filed Jul. 20, 2005 and entitled “METHODAND APPARATUS FOR BOUNDARY-BASED NETWORK OPERATION”, which isincorporated herein by reference in its entirety, may be utilized inconjunction with the present invention. As disclosed therein, theidentity of a subscriber device or subscriber is anonymized by using acryptographic hash coupled with an optional “opaque” variable whichcarries information relating to the subscriber device of the hash withwhich it is associated. The hash and opaque variable frustratede-encryption or reverse-engineering of the individual subscriber'sidentity or specific location. Alternative methods of providinganonymization may also be utilized consistent with the presentinvention.

While complete anonymization (i.e., there is no way of tracing oridentifying the source) is generally not applicable to information whichmust be used to uniquely identify an individual and/or device, partialanonymization such as that described above is readily used with thepresent invention. For example, it may be desirable to perform a one-wayhash of a user's IP address or MAC address so that someonesurreptitiously obtaining the information cannot determine the sourcedata (actual address), but the hash algorithm produces a knowndeterministic result with the same “seed”, and hence the hash output canbe used to uniquely identify a given user/device, such as by matchingthat hashed output with known outputs from the same algorithmcorresponding to existing subscribers/devices. This hashing is to bedistinguished from encryption, wherein the original source data(address) can in fact be recovered and read when the encrypted data isdecrypted (such as via a public/private encryption key pair).

Business/Operational Rules Engine—

In another aspect of the invention, a so-called “decision” engine may bedisposed at e.g., the identity provider 210, entitlement server 208,service provider 202, content server 206, CPE 106, or other location(e.g., rendered as one or more computer programs disposed thereon). Thisengine comprises, in an exemplary embodiment, one or more softwareroutines adapted to control the authentication/authorization and contentdelivery processes in order to achieve one or more goals relating tooperations or business (e.g., profit or revenue or subscriberretention). Included within these areas are network optimization andreliability goals, increased maintenance intervals, increased subscriberor user satisfaction/longevity, increased subscription base, higherprofit (e.g., from increased advertising revenues, more subscriber“views” of given content, greater flexibility in the types and locationsof platforms from which the subscriber may access content, and soforth).

These decision rules may comprise a separate entity or process, and mayalso be fully integrated within other processing entities (such as theapplications running on the aforementioned entities and/or the clientapplication), and controlled via e.g., a GUI displayed on a deviceconnected to the relevant server, network entity, or even CPE 106. Ineffect, the rules engine comprises a supervisory entity which monitorsand selectively controls content access and delivery operation at ahigher level, so as to implement desired operational or business rules.The decision engine can be considered an overlay of sorts to the morefundamental algorithms used to accomplish required network operation.

For example, the identity provider 210, entitlement server 208, serviceprovider 202, content server 206, and/or CPE 106 may invoke certainoperational protocols or decision processes based on information orrequests received from the CPE 106 or PMD 107, conditions existingwithin the network, demographic data, geographic data, etc. However,these processes may not always be compatible with higher-level businessor operational goals, such as maximizing profit or system reliability.Hence, when imposed, the business/operational rules can be used todynamically (or manually) control access to and delivery of content. Thedecision rules may be, e.g., operational or business-oriented in nature,and may also be applied selectively in terms of time of day, duration,specific local areas, or even at the individual user level (e.g., viaspecific identification of the CPE or client device via TUNER_ID, IPaddress, MAC address, or the like, or via a user-based login or“entitlements” profile of the type previously described herein).

For example, one decision rule implemented by the decision engine maycomprise providing protected content from the third party (e.g., serviceprovider 202) according to a tiered system. Content under such anapproach might be selected in part on the revenue such delivery willbring to the MSO 201 based on the content source.

Various billing models for the delivery of protected content may also beincorporated into the rules engine. The rules engine may include forinstance various policies which provide information that is utilized bye.g., billing entities to generate billing records. For example, theengine may include rules for applying a pricing structure to requestedcontent. In one embodiment, the rules may indicate a pre-selected amountof content hours and/or particular content which is offered to certainsubscribers without a fee. Additional fees may be charged for premiumcontent, content which is outside a subscriber's subscription plan,pay-per-view content, and/or for content exceeding a prescribed timethreshold (e.g., content hours requested above those hours which areincluded in the subscriber's subscription plan). Hence, when content isrequested the rules engine may consult the pricing structure andgenerate a record of a cost to be charged to the customer. The recordmay be used to generate a bill as well as to inform the customer of theadditional costs. The rules engine may further be constructed so thatthe content is delivered only after the customer has given permissionfor the additional charges. The ability of the MSO to make an “upsell”;i.e., offer the consumer an opportunity to purchase a higher tiersubscription and/or pay-per-use subscriptions.

The various billing rules may further take into account the customer'ssubscription level. For example, certain customers may be affordedaccess to certain types of content at no additional charges, whereasother customers may be required to pay additional fees to receive thecontent. Suppose for example a customer has a “basic” subscription whichincludes content which is broadcast on Channel X, but does not includecontent which is broadcast on Channel Y. If the subscriber requestscontent which is broadcast on Channel X, the rules engine consults thepricing structure (and other rules), and determines that the subscriberis within his/her subscription plan in requesting the content, and doesnot apply a price (e.g., generate information to be used in generating abilling record). If that subscriber instead requests content which isbroadcast on Channel Y, the rules engine consults the pricing structure(and other rules) and determines that the subscriber is outside ofhis/her subscription plan, and thus applies a price model to thecontent. The rules engine may further inquire for permissions given thedetermined price, and pass the pricing information to a billing entity.

Additionally content may be established with the rules engine as free,or have a set price. For example, free on-demand (FOD) content may beindicated at the rules engine as never having a price associatedtherewith, whereas VOD, movies on-demand (MOD), and pay-per-view contentmay be associated with a pricing structure. In another variant, asubscriber may be entitled to a certain number of requests and/or a timelimit for receiving content. For example, a customer's subscription planmay be associated with a certain number or hours of content access(e.g., unlimited, 1 request per month, 10 hours of content downloads,etc.). As discussed above, the rules engine applies a pricing structure(as applicable) upon user request.

In yet another variant, the use rights or features provided with therequested (protected) content may be varied as a function of e.g.,subscriber subscription level, time of day, requesting devicecapability, etc. For instance, a request received from a premium level,or “Gold”, subscriber might be serviced with a content stream thatincludes complete “trick mode” functionality (i.e., FF, REW, Pause,etc.), or for broadcasts a “start over” functionality, whereas a lowertier subscriber's request might not include one or any of thesecapabilities. The number of plays can be limited as well; e.g., Goldsubscribers receive unlimited plays, while lower tiers receive only oneor a finite number of plays of the content. As noted above, these rulesor functional restrictions can be relayed from the MSO 201 to theservice provider 202 via messaging conducted pursuant to a particularsubscriber request, or alternatively can be pre-positioned within theservice provider site as a decision rule set. Moreover, the quality ofcontent provided can be varied as needed or desired. For instance, useof different encodings or bitrates (e.g., HD versus SD), QoS parameters,latency, etc. can be employed depending on the subscriber(individually), the general classification of the subscriber (e.g.,Gold), time of day, available resources, revenue/profit implications ofeach option, etc.

It will also be recognized that both the MSO 201 and the third party(e.g., service provider 202) may employ different business or operationdecision rules to one another. For example, the MSO 201 might establishpreferential rules or classes for the various service providers 202,such that service provided to these different providers 202 isdifferentiated in some fashion. In one such case, those providers 202paying the MSO 201 a fee, or with which the MSO 201 has a pre-existingbusiness relationship, may be given preferential service andcapabilities.

The MSO 201 and/or service provider 202 may also structure a businessrelationship whereby one “pays” the other via some sort of considerationfor servicing of requests. For example, an MSO might pay a givenprovider $X for each valid MSO subscriber request serviced by theprovider, since the MSO is in effect leveraging the programmer'sinfrastructure to extend the reach of its capabilities for the MSOcustomers (i.e., extension of the “four any's” model described inco-owned U.S. Provisional Application Ser. No. 61/256,903 entitled“METHODS AND APPARATUS FOR PACKETIZED CONTENT DELIVERY OVER A CONTENTDELIVERY NETWORK” previously incorporated herein. Conversely, theprovider might pay the MSO consideration for each MSO subscriber requestserviced, or an advertisement click-through basis, etc. in that if theMSO instructs its subscribers to use the provider's site preferentiallyover others, this may generate additional revenue (such as via theaforementioned click-throughs) for the provider or its advertisers.

As noted above, certain information may be collected and utilized toprovide targeted advertisements to the CPE. For example, the methods andapparatus of co-owned, co-pending U.S. patent application Ser. No.11/441,476 filed on May 24, 2006 and entitled “SECONDARY CONTENTINSERTION APPARATUS AND METHODS” and/or co-owned, co-pending U.S. patentapplication Ser. No. 11/198,620 filed on Aug. 4, 2005 and entitled“METHOD AND APPARATUS FOR CONTEXT-SPECIFIC CONTENT DELIVERY”, each ofwhich is incorporated herein by reference in its entirety, may beutilized to provide dynamic secondary content insertion (e.g.,replacement of dated or geographically inappropriate advertisements orpromotions) and/or contextually-related “secondary” content (e.g.,advertising messages, useful informational links, etc.). Still further,collected information regarding a user's viewing habits may be utilizedto provide content recommendations as discussed in co-owned, co-pendingU.S. patent application Ser. No. 12/414,576 filed Mar. 30, 2009 andentitled “RECOMMENDATION ENGINE APPARATUS AND METHODS”, which isincorporated herein by reference in its entirety.

Content, user interface and/or advertisement personalization may also beprovided.

Many other approaches and combinations of various operational andbusiness paradigms are envisaged consistent with the invention, as willbe recognized by those of ordinary skill when provided this disclosure.

It will be recognized that while certain aspects of the invention aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of theinvention, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the invention disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the invention as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the invention. Theforegoing description is of the best mode presently contemplated ofcarrying out the invention. This description is in no way meant to belimiting, but rather should be taken as illustrative of the generalprinciples of the invention. The scope of the invention should bedetermined with reference to the claims.

1. A method for providing protected content via a first network to anauthorized user of a second network, said method comprising: receivingat an entity of said second network a request for said protectedcontent, said request comprising at least information identifying arequesting user and information identifying requested content;determining, based at least in part on said information identifying saidrequesting user, an identity of said requesting user as an authorizeduser of said second network; generating a unique identifier for saidauthorized user; and transmitting a response to said request to anentity of said first network, said response comprising said uniqueidentifier; wherein, said transmission of said response is configured tocause said entity of said first network deliver said protected contentto said authorized user; and wherein said unique identifier is stored atsaid entity of said first network and is configured to enable use in asubsequent request, said subsequent request comprising a request forsecond protected content different than said first content.
 2. Themethod of claim 1, wherein said information identifying said usercomprises login information pre-established at said entity of saidsecond network to correspond to said authorized user.
 3. The method ofclaim 1, wherein said act of generating said unique identifier for saidauthorized user comprises generating a user-specific global uniqueidentifier (GTJID).
 4. The method of claim 1, wherein said secondsubsequent request for said second protected content having said uniqueidentifier therein enables said entity of said first network to identifysaid authorized user and transmit a response to said second requestbased thereon.
 5. An apparatus in a content delivery network configuredto authorize access to a selected one or more services at a packetnetwork by at least one user device, said apparatus comprising: a firstinterface configured to receive: information identifying said at leastone user device; and a request for said access to said selected one ormore services; a processor comprising at least one computer program,said computer program configured to: verify said information identifyingsaid at least one user device as being associated with at least onesubscriber of said content delivery network; generate a uniqueidentifier specific to said subscriber; and generate a response to saidrequest for said access to said selected one or more services; and asecond interface configured to transmit: said unique identifier to atleast one entity of said packet network for storage thereon; and saidresponse to said request for said access to said selected one or moreservices.
 6. The apparatus of claim 5, wherein said at least one entityof said packet network is configured to provide said stored uniqueidentifier in subsequent requests from said at least one user device fora second at least one of said one or more services.
 7. The apparatus ofclaim 5, wherein said response to said request comprises a communicationwhich causes said at least one user device to establish a session withsaid at least one entity of said packet network, and to receive saidselected one or more services via said established session.
 8. Themethod of claim 5, wherein the packet network comprises a serviceprovider in communication with said one or more registered devices viathe Internet, and said content delivery network comprises a cabletelevision network in communication with said service provider via theInternet.
 9. The method of claim 5, wherein said one or more servicescomprise on-demand delivery of available programming content.
 10. Themethod of claim 5, further comprising transmitting a request to removesaid at least one unique identifier from said storage at said packetnetwork, and, in response to said request removing said at least oneunique identifier from said storage at said packet network.
 11. A methodfor providing protected content via a first content delivery network toan authorized user of a second content delivery network, said methodcomprising: receiving at an entity of said first network a request forsaid protected content from a user device, said request comprising atleast information identifying said user device and informationidentifying said protected content; querying a plurality of records todetermine a unique identifier of said user device, said uniqueidentifier being previously provided by said second network;transmitting said unique identifier and said information identifyingsaid protected content to an entity of said second network; receiving inresponse to said transmission of said unique identifier and saidinformation identifying said protected content, a response from saidentity of said second network; and delivering said protected content tosaid user device based at least in part on said response.
 12. The methodof claim 11, wherein said first network comprises a packet switchednetwork, and said second network comprises a substantiallycircuit-switched content delivery network.
 13. The method of claim 12,wherein said packet switched network comprises an IP (Internet Protocol)Multimedia Services (IMS) entity.
 14. The method of claim 11, furthercomprising initiating a Session Initiation Protocol (SIP) sessionbetween said entity of said first network and said user device.
 15. Themethod of claim 14, wherein said request comprises receiving a SIPmessage from said user device, the SIP message including one or moreidentifiers of said protected content.
 16. A method of operating apacket network, comprising: receiving from an IP-enabled device arequest for content at an entity of said packet network, said contentbeing protected in accordance with one or more policies specified by theoperator of a managed content distribution network, said requestcomprising information uniquely associated with a subscriber of saidmanaged network; accessing information stored at said entity receivedfrom said operator, said stored information enabling said entity todetermine whether the request for content should be granted; whengranting said request, issuing a communication to said managed networkindicating that said content is being provided; and causing said contentto be provided to said requesting 1P-enabled device over said packetnetwork, said content being at least partly encapsulated using an IPprotocol.
 17. The method of claim 16, wherein said communicationcomprises a message identifying both said content and at least one of:(i) the subscriber, and/or (ii) the IP-enabled device.
 18. The method ofclaim 16, wherein said communication is agnostic to the underlyingtransport over which it is carried to said managed network.
 19. Themethod of claim 16, wherein said act of causing said content to beprovided to said requesting IP-enabled device over said packet networkcomprises encrypting said content using an encryption mechanism that issubstantially unique to said subscriber.
 20. The method of claim 19,wherein said encryption mechanism that is substantially unique to saidsubscriber comprises a public/private key pair assigned to saidsubscriber by said managed network operator.
 21. The method of claim 16,wherein said information stored at said entity received from saidoperator comprises configuration information relating to at least oneaspect of said IP-enabled device.